From: patchwork-bot+netdevbpf@kernel.org
To: Yuyang Huang <yuyanghuang@google.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
idosch@nvidia.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] ipv4: igmp: annotate diagnostic procfs data races
Date: Tue, 09 Jun 2026 11:30:09 +0000 [thread overview]
Message-ID: <178100460914.1971667.2337389980081963342.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260605014318.3890804-1-yuyanghuang@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 5 Jun 2026 10:43:16 +0900 you wrote:
> This patch series addresses several unannotated data races between lockless
> RCU-protected diagnostic reads in /proc/net/igmp (igmp_mc_seq_show())
> and concurrent writes in serialized paths (RTNL and group spinlocks).
>
> Following the precedent in commit 061c0aa740d5 ("ipv4: igmp: annotate
> data-races around im->users"), we annotate these intentional data races
> using READ_ONCE() and WRITE_ONCE() macros.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] ipv4: igmp: annotate data-races around in_dev->mc_count
https://git.kernel.org/netdev/net-next/c/1719841cab55
- [net-next,v2,2/2] ipv4: igmp: annotate data-races around timer-related fields
https://git.kernel.org/netdev/net-next/c/3289d17b7a13
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:[~2026-06-09 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 1:43 [PATCH net-next v2 0/2] ipv4: igmp: annotate diagnostic procfs data races Yuyang Huang
2026-06-05 1:43 ` [PATCH net-next v2 1/2] ipv4: igmp: annotate data-races around in_dev->mc_count Yuyang Huang
2026-06-05 1:43 ` [PATCH net-next v2 2/2] ipv4: igmp: annotate data-races around timer-related fields Yuyang Huang
2026-06-09 11:30 ` 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=178100460914.1971667.2337389980081963342.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuyanghuang@google.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