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, razor@blackwall.org, idosch@nvidia.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v3 net-next 00/11] bridge: prepare lockless br_port_fill_attrs() (I)
Date: Sat, 06 Jun 2026 01:00:24 +0000 [thread overview]
Message-ID: <178070762414.3975748.5475369779498083392.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260604141343.2124500-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 4 Jun 2026 14:13:32 +0000 you wrote:
> medium-term goal is to allow "ip link show" dump commands to run without RTNL.
>
> This round of patches adds/fixes some lockess accesses in bridge.
>
> This is not complete, more patches will come later.
>
> Ultimately all changes to p->flags should use set_bit()/clear_bit().
>
> [...]
Here is the summary with links:
- [v3,net-next,01/11] bridge: add a READ_ONCE() in br_timer_value()
https://git.kernel.org/netdev/net-next/c/032c8f6f21ee
- [v3,net-next,02/11] bridge: add bridge_flags_bit enum
https://git.kernel.org/netdev/net-next/c/87020def2529
- [v3,net-next,03/11] bridge: use BR_PROMISC_BIT
https://git.kernel.org/netdev/net-next/c/f8bcd3075725
- [v3,net-next,04/11] bridge: use BR_ADMIN_COST_BIT
https://git.kernel.org/netdev/net-next/c/2013ebb9b381
- [v3,net-next,05/11] bridge: provide lockless access to p->path_cost
https://git.kernel.org/netdev/net-next/c/f236240c9beb
- [v3,net-next,06/11] bridge: provide lockless access to p->designated_cost
https://git.kernel.org/netdev/net-next/c/5deaf0495158
- [v3,net-next,07/11] bridge: provide lockless access to p->designated_port
https://git.kernel.org/netdev/net-next/c/009b1dc8bf64
- [v3,net-next,08/11] bridge: provide lockless access to p->priority
https://git.kernel.org/netdev/net-next/c/abe46dbe52da
- [v3,net-next,09/11] bridge: provide lockless access to p->port_id
https://git.kernel.org/netdev/net-next/c/6d39b5d08009
- [v3,net-next,10/11] bridge: provide lockless access to p->config_pending
https://git.kernel.org/netdev/net-next/c/f51657cd7227
- [v3,net-next,11/11] bridge: read p->flags once in br_port_fill_attrs()
https://git.kernel.org/netdev/net-next/c/0733947606dd
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-06 1:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 14:13 [PATCH v3 net-next 00/11] bridge: prepare lockless br_port_fill_attrs() (I) Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 01/11] bridge: add a READ_ONCE() in br_timer_value() Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 02/11] bridge: add bridge_flags_bit enum Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 03/11] bridge: use BR_PROMISC_BIT Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 04/11] bridge: use BR_ADMIN_COST_BIT Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 05/11] bridge: provide lockless access to p->path_cost Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 06/11] bridge: provide lockless access to p->designated_cost Eric Dumazet
2026-06-04 18:43 ` Ido Schimmel
2026-06-04 14:13 ` [PATCH v3 net-next 07/11] bridge: provide lockless access to p->designated_port Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 08/11] bridge: provide lockless access to p->priority Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 09/11] bridge: provide lockless access to p->port_id Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 10/11] bridge: provide lockless access to p->config_pending Eric Dumazet
2026-06-04 14:13 ` [PATCH v3 net-next 11/11] bridge: read p->flags once in br_port_fill_attrs() Eric Dumazet
2026-06-06 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=178070762414.3975748.5475369779498083392.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=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
/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