All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: davem@davemloft.net, kuba@kernel.org, linux-nfc@lists.01.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/1] nfc: llcp: a fix after syzbot report
Date: Wed, 19 Jan 2022 14:20:10 +0000	[thread overview]
Message-ID: <164260201060.5270.11254904971363048637.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220119074816.6505-1-krzysztof.kozlowski@canonical.com>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Wed, 19 Jan 2022 08:48:15 +0100 you wrote:
> Hi,
> 
> Syzbot reported an easily reproducible NULL pointer dereference which I was
> struggling to analyze:
> https://syzkaller.appspot.com/bug?extid=7f23bcddf626e0593a39
> 
> Although direct fix is obvious, I could not actually find the exact race
> condition scenario leading to it.  The patch fixes the issue - at least under
> my QEMU - however all this code looks racy, so I have a feeling I am plumbing
> one leak without fixing root cause.
> 
> [...]

Here is the summary with links:
  - [v2,1/1] nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind()
    https://git.kernel.org/netdev/net/c/dded08927ca3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-01-19 14:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19  7:48 [PATCH v2 0/1] nfc: llcp: a fix after syzbot report Krzysztof Kozlowski
2022-01-19  7:48 ` Krzysztof Kozlowski
2022-01-19  7:48 ` [linux-nfc] " Krzysztof Kozlowski
2022-01-19  7:48 ` [PATCH v2 1/1] nfc: llcp: fix NULL error pointer dereference on sendmsg() after failed bind() Krzysztof Kozlowski
2022-01-19  7:48   ` Krzysztof Kozlowski
2022-01-19  7:48   ` [linux-nfc] " Krzysztof Kozlowski
2022-01-19 14:20 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=164260201060.5270.11254904971363048637.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfc@lists.01.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.