From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, kuniyu@google.com, andrew+netdev@lunn.ch,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/2] vlan: lockless vlan_fill_info()
Date: Sat, 19 Sep 2026 00:10:19 +0000 [thread overview]
Message-ID: <178977661914.1197442.12574021700995796007.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260916132532.1785657-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 16 Sep 2026 13:25:30 +0000 you wrote:
> vlan_fill_info() currently relies on RTNL being held, because it
> uses rcu_dereference_rtnl() to walk vlan->egress_priority_map[].
>
> While auditing the fields exposed there, it appears that
> vlan->flags, vlan->ingress_priority_map[] and vlan->nr_*_mappings
> are written under RTNL but already read from lockless contexts
> (RX, TX, /proc/net/vlan/<dev> and vlan_get_size()).
>
> [...]
Here is the summary with links:
- [net-next,1/2] vlan: annotate data-races in vlan_dev_priv fields
https://git.kernel.org/netdev/net-next/c/ca6ff8dd70eb
- [net-next,2/2] vlan: no longer rely on RTNL in vlan_fill_info()
https://git.kernel.org/netdev/net-next/c/ea5bd52c8bdd
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-09-19 0:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 13:25 [PATCH net-next 0/2] vlan: lockless vlan_fill_info() Eric Dumazet
2026-09-16 13:25 ` [PATCH net-next 1/2] vlan: annotate data-races in vlan_dev_priv fields Eric Dumazet
2026-09-16 13:25 ` [PATCH net-next 2/2] vlan: no longer rely on RTNL in vlan_fill_info() Eric Dumazet
2026-09-19 0:10 ` 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=178977661914.1197442.12574021700995796007.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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