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, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/2] macvlan: RTNL-less macvlan_fill_info()
Date: Fri, 03 Jul 2026 16:40:08 +0000 [thread overview]
Message-ID: <178309680863.3234711.6167695440715149504.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260701082214.2974946-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 1 Jul 2026 08:22:12 +0000 you wrote:
> This series removes the RTNL lock dependency from macvlan_fill_info(),
> allowing it to run under RCU read lock.
>
> The first patch annotates data races on 'mode' and 'flags' fields which
> are accessed locklessly in the RX/TX paths.
>
> The second patch transitions macvlan_fill_info() to RCU, adding necessary
> annotations for other fields and handling concurrent updates to the MAC
> address list by computing the count dynamically.
>
> [...]
Here is the summary with links:
- [net-next,1/2] macvlan: annotate data-races around vlan->mode and vlan->flags
https://git.kernel.org/netdev/net-next/c/ed37710d6c67
- [net-next,2/2] macvlan: no longer rely on RTNL in macvlan_fill_info()
https://git.kernel.org/netdev/net-next/c/6d728e7e286b
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-07-03 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 8:22 [PATCH net-next 0/2] macvlan: RTNL-less macvlan_fill_info() Eric Dumazet
2026-07-01 8:22 ` [PATCH net-next 1/2] macvlan: annotate data-races around vlan->mode and vlan->flags Eric Dumazet
2026-07-01 12:09 ` Nikolay Aleksandrov
2026-07-01 22:11 ` Kuniyuki Iwashima
2026-07-01 8:22 ` [PATCH net-next 2/2] macvlan: no longer rely on RTNL in macvlan_fill_info() Eric Dumazet
2026-07-01 12:11 ` Nikolay Aleksandrov
2026-07-01 22:14 ` Kuniyuki Iwashima
2026-07-03 16:40 ` 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=178309680863.3234711.6167695440715149504.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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