From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, tobias@waldekranz.com, kuba@kernel.org,
roopa@nvidia.com, bridge@lists.linux.dev, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org
Subject: Re: [PATCH net 0/2] net: bridge: mst: fix suspicious rcu usage warning
Date: Thu, 13 Jun 2024 02:00:30 +0000 [thread overview]
Message-ID: <171824403056.29575.16184677059913540404.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240609103654.914987-1-razor@blackwall.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 9 Jun 2024 13:36:52 +0300 you wrote:
> Hi all,
> This set fixes a suspicious RCU usage warning triggered by syzbot[1] in
> the bridge's MST code. After I converted br_mst_set_state to RCU, I
> forgot to update the vlan group dereference helper. Fix it by using
> the proper helper, in order to do that we need to pass the vlan group
> which is already obtained correctly by the callers for their respective
> context. Patch 01 is a requirement for the fix in patch 02.
>
> [...]
Here is the summary with links:
- [net,1/2] net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state
https://git.kernel.org/netdev/net/c/36c92936e868
- [net,2/2] net: bridge: mst: fix suspicious rcu usage in br_mst_set_state
https://git.kernel.org/netdev/net/c/546ceb1dfdac
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:[~2024-06-13 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 10:36 [PATCH net 0/2] net: bridge: mst: fix suspicious rcu usage warning Nikolay Aleksandrov
2024-06-09 10:36 ` [PATCH net 1/2] net: bridge: mst: pass vlan group directly to br_mst_vlan_set_state Nikolay Aleksandrov
2024-06-09 10:36 ` [PATCH net 2/2] net: bridge: mst: fix suspicious rcu usage in br_mst_set_state Nikolay Aleksandrov
2024-06-13 2:00 ` 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=171824403056.29575.16184677059913540404.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bridge@lists.linux.dev \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
--cc=tobias@waldekranz.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).