From: patchwork-bot+netdevbpf@kernel.org
To: Yuyang Huang <sigefriedhyy@gmail.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] ipv6: mcast: annotate data races in /proc/net/igmp6
Date: Sat, 13 Jun 2026 00:30:27 +0000 [thread overview]
Message-ID: <178131062788.1306549.10543327145544730405.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609081113.7613-1-sigefriedhyy@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 9 Jun 2026 17:11:11 +0900 you wrote:
> /proc/net/igmp6 walks IPv6 multicast memberships under RCU without
> holding idev->mc_lock, taking a lockless snapshot of two fields that
> writers update under the lock: mca_flags and mca_work.timer.expires.
>
> Patch 1 adds WRITE_ONCE() to all mca_flags update sites and READ_ONCE()
> to the procfs reader. Patch 2 does the same for the timer.expires read
> in the procfs path.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] ipv6: mcast: annotate data-races around mca_flags
https://git.kernel.org/netdev/net-next/c/d0dc208808a2
- [net-next,v2,2/2] ipv6: mcast: annotate igmp6 timer expiry race
https://git.kernel.org/netdev/net-next/c/1ea2f885a76b
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-13 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 8:11 [PATCH net-next v2 0/2] ipv6: mcast: annotate data races in /proc/net/igmp6 Yuyang Huang
2026-06-09 8:11 ` [PATCH net-next v2 1/2] ipv6: mcast: annotate data-races around mca_flags Yuyang Huang
2026-06-09 9:36 ` Eric Dumazet
2026-06-09 10:39 ` Yuyang Huang
2026-06-11 6:31 ` Ido Schimmel
2026-06-09 8:11 ` [PATCH net-next v2 2/2] ipv6: mcast: annotate igmp6 timer expiry race Yuyang Huang
2026-06-11 6:32 ` Ido Schimmel
2026-06-13 0: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=178131062788.1306549.10543327145544730405.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=sigefriedhyy@gmail.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.