From: patchwork-bot+netdevbpf@kernel•org
To: Jeremy Cline <jeremy@jcline•org>
Cc: krzysztof.kozlowski@linaro•org, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
netdev@vger•kernel.org, linux-kernel@vger•kernel.org,
syzbot+c1d0a03d305972dbbe14@syzkaller•appspotmail.com
Subject: Re: [PATCH net] net: nfc: llcp: Add lock when modifying device list
Date: Tue, 03 Oct 2023 15:40:26 +0000 [thread overview]
Message-ID: <169634762615.3806.18178372938217488177.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230908235853.1319596-1-jeremy@jcline.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Fri, 8 Sep 2023 19:58:53 -0400 you wrote:
> The device list needs its associated lock held when modifying it, or the
> list could become corrupted, as syzbot discovered.
>
> Reported-and-tested-by: syzbot+c1d0a03d305972dbbe14@syzkaller•appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=c1d0a03d305972dbbe14
> Signed-off-by: Jeremy Cline <jeremy@jcline•org>
>
> [...]
Here is the summary with links:
- [net] net: nfc: llcp: Add lock when modifying device list
https://git.kernel.org/netdev/net/c/dfc7f7a988da
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-03 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 23:58 [PATCH net] net: nfc: llcp: Add lock when modifying device list Jeremy Cline
2023-09-10 15:28 ` Simon Horman
2023-09-10 23:06 ` Jeremy Cline
2023-09-11 5:59 ` Simon Horman
2023-09-11 12:52 ` Simon Horman
2023-09-12 15:40 ` Jeremy Cline
2023-10-03 15:40 ` 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=169634762615.3806.18178372938217488177.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=jeremy@jcline$(echo .)org \
--cc=krzysztof.kozlowski@linaro$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=syzbot+c1d0a03d305972dbbe14@syzkaller$(echo .)appspotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox