All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	idosch@nvidia.com, dsahern@kernel.org, horms@kernel.org,
	netdev@vger.kernel.org, eric.dumazet@gmail.com,
	syzbot+3d99fb01bcd740f2fc1e@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 net] igmp: convert struct ip_sf_list to RCU
Date: Tue, 01 Sep 2026 01:00:10 +0000	[thread overview]
Message-ID: <178822441089.861275.11689681327779869610.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260827160656.903003-1-edumazet@google.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 27 Aug 2026 16:06:56 +0000 you wrote:
> Commit 23d2b94043ca ("igmp: Add ip_mc_list lock in ip_check_mc_rcu")
> added spin_lock_bh(&im->lock) to ip_check_mc_rcu() to prevent a
> use-after-free while iterating im->sources during concurrent deletions.
> 
> However, ip_check_mc_rcu() is called from RCU read-side critical
> sections in packet receive and route lookup fast paths (e.g.
> __mkroute_output(), ip_route_input_rcu(), and __udp4_lib_rcv()).
> 
> [...]

Here is the summary with links:
  - [v2,net] igmp: convert struct ip_sf_list to RCU
    https://git.kernel.org/netdev/net/c/2987ee196c88

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



      parent reply	other threads:[~2026-09-01  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 16:06 [PATCH v2 net] igmp: convert struct ip_sf_list to RCU Eric Dumazet
2026-08-30  9:52 ` Ido Schimmel
2026-09-01  1: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=178822441089.861275.11689681327779869610.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+3d99fb01bcd740f2fc1e@syzkaller.appspotmail.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 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.