From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com, andy@greyhouse.net,
johannes.berg@intel.com, jiri@nvidia.com
Subject: Re: [PATCH net-next] net: bonding: correctly annotate RCU in bond_should_notify_peers()
Date: Tue, 23 Jul 2024 13:20:32 +0000 [thread overview]
Message-ID: <172174083282.27427.8145333747572048841.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240719094119.35c62455087d.I68eb9c0f02545b364b79a59f2110f2cf5682a8e2@changeid>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 19 Jul 2024 09:41:18 -0700 you wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> RCU use in bond_should_notify_peers() looks wrong, since it does
> rcu_dereference(), leaves the critical section, and uses the
> pointer after that.
>
> Luckily, it's called either inside a nested RCU critical section
> or with the RTNL held.
>
> [...]
Here is the summary with links:
- [net-next] net: bonding: correctly annotate RCU in bond_should_notify_peers()
https://git.kernel.org/netdev/net/c/3ba359c0cd6e
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-07-23 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 16:41 [PATCH net-next] net: bonding: correctly annotate RCU in bond_should_notify_peers() Johannes Berg
2024-07-21 17:09 ` Jay Vosburgh
2024-07-23 10:25 ` Paolo Abeni
2024-07-23 11:30 ` Johannes Berg
2024-07-23 13:12 ` Paolo Abeni
2024-07-23 13: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=172174083282.27427.8145333747572048841.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=j.vosburgh@gmail.com \
--cc=jiri@nvidia.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--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 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).