From: Ido Schimmel <idosch@nvidia.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: bridge@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Nikolay Aleksandrov <razor@blackwall.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Simon Horman <horms@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Kuniyuki Iwashima <kuniyu@google.com>,
Stanislav Fomichev <sdf@fomichev.me>,
Xiao Liang <shaw.leon@gmail.com>
Subject: Re: [PATCH net-next v2 11/14] net: bridge: mcast: track active state, prepare for outside lock reads
Date: Sun, 8 Feb 2026 18:11:26 +0200 [thread overview]
Message-ID: <20260208161126.GK154003@shredder> (raw)
In-Reply-To: <20260206030123.5430-12-linus.luessing@c0d3.blue>
On Fri, Feb 06, 2026 at 03:52:17AM +0100, Linus Lüssing wrote:
> @@ -1095,23 +1095,25 @@ static void br_ip6_multicast_update_active(struct net_bridge_mcast *brmctx,
> {
> #if IS_ENABLED(CONFIG_IPV6)
> if (force_inactive)
> - brmctx->ip6_active = false;
> + WRITE_ONCE(brmctx->ip6_active, false);
> else
> - brmctx->ip6_active = br_ip6_multicast_querier_exists(brmctx);
> + WRITE_ONCE(brmctx->ip6_active, br_ip6_multicast_querier_exists(brmctx));
> #endif
> }
>
> static void br_multicast_notify_active(struct net_bridge_mcast *brmctx,
> bool ip4_active_old, bool ip6_active_old)
> {
> - if (brmctx->ip4_active == ip4_active_old &&
> - brmctx->ip6_active == ip6_active_old)
> + int ip4_active = READ_ONCE(brmctx->ip4_active);
> + int ip6_active = READ_ONCE(brmctx->ip6_active);
I believe that this is unnecessary since we are holding the lock and it
will confuse people reading the code. We only need the READ_ONCE() later
on in the data path
> +
> + if (ip4_active == ip4_active_old &&
> + ip6_active == ip6_active_old)
> return;
>
> br_info(brmctx->br, "mc_active changed, vid: %i: v4: %i->%i, v6: %i->%i\n",
> brmctx->vlan ? brmctx->vlan->vid : -1,
> - ip4_active_old, brmctx->ip4_active,
> - ip6_active_old, brmctx->ip6_active);
> + ip4_active_old, ip4_active, ip6_active_old, ip6_active);
> }
>
> /**
> @@ -1136,7 +1138,8 @@ static void br_multicast_notify_active(struct net_bridge_mcast *brmctx,
> */
> static void br_multicast_update_active(struct net_bridge_mcast *brmctx)
> {
> - bool ip4_active_old = brmctx->ip4_active, ip6_active_old = brmctx->ip6_active;
> + bool ip4_active_old = READ_ONCE(brmctx->ip4_active);
> + bool ip6_active_old = READ_ONCE(brmctx->ip6_active);
Same
> bool force_inactive = false;
>
> lockdep_assert_held_once(&brmctx->br->multicast_lock);
> @@ -4266,13 +4269,13 @@ void br_multicast_ctx_init(struct net_bridge *br,
> brmctx->multicast_membership_interval = 260 * HZ;
>
> brmctx->ip4_querier.port_ifidx = 0;
> - brmctx->ip4_active = 0;
> + WRITE_ONCE(brmctx->ip4_active, 0);
> seqcount_spinlock_init(&brmctx->ip4_querier.seq, &br->multicast_lock);
> brmctx->multicast_igmp_version = 2;
> #if IS_ENABLED(CONFIG_IPV6)
> brmctx->multicast_mld_version = 1;
> brmctx->ip6_querier.port_ifidx = 0;
> - brmctx->ip6_active = 0;
> + WRITE_ONCE(brmctx->ip6_active, 0);
> seqcount_spinlock_init(&brmctx->ip6_querier.seq, &br->multicast_lock);
> #endif
>
> --
> 2.51.0
>
next prev parent reply other threads:[~2026-02-08 16:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 2:52 [PATCH net-next v2 00/14] net: bridge: reduce multicast checks in fast path Linus Lüssing
2026-02-06 2:52 ` [PATCH net-next v2 01/14] net: bridge: mcast: export ip{4,6}_active state to netlink Linus Lüssing
2026-02-08 16:00 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 02/14] net: bridge: mcast: track active state, adding tests Linus Lüssing
2026-02-07 4:58 ` Jakub Kicinski
2026-02-08 16:00 ` Ido Schimmel
2026-02-10 21:06 ` Linus Lüssing
2026-02-11 9:42 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 03/14] net: bridge: mcast: avoid sleeping on bridge-down Linus Lüssing
2026-02-08 11:41 ` Ido Schimmel
2026-02-08 16:01 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 04/14] net: bridge: mcast: track active state, IGMP/MLD querier appearance Linus Lüssing
2026-02-08 16:07 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 05/14] net: bridge: mcast: track active state, foreign IGMP/MLD querier disappearance Linus Lüssing
2026-02-07 4:56 ` [net-next,v2,05/14] " Jakub Kicinski
2026-02-11 3:05 ` Linus Lüssing
2026-02-08 16:08 ` [PATCH net-next v2 05/14] " Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 06/14] net: bridge: mcast: track active state, IPv6 address availability Linus Lüssing
2026-02-08 16:08 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 07/14] net: bridge: mcast: track active state, own MLD querier disappearance Linus Lüssing
2026-02-08 16:09 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 08/14] net: bridge: mcast: track active state, if snooping is enabled Linus Lüssing
2026-02-08 16:09 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 09/14] net: bridge: mcast: track active state, VLAN snooping Linus Lüssing
2026-02-08 16:10 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 10/14] net: bridge: mcast: track active state, bridge up/down Linus Lüssing
2026-02-08 16:10 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 11/14] net: bridge: mcast: track active state, prepare for outside lock reads Linus Lüssing
2026-02-08 16:11 ` Ido Schimmel [this message]
2026-02-06 2:52 ` [PATCH net-next v2 12/14] net: bridge: mcast: use combined active state in netlink Linus Lüssing
2026-02-08 16:11 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 13/14] net: bridge: mcast: use combined active state in fast/data path Linus Lüssing
2026-02-08 16:12 ` Ido Schimmel
2026-02-06 2:52 ` [PATCH net-next v2 14/14] net: bridge: mcast: add inactive state assertions Linus Lüssing
2026-02-08 16:13 ` Ido Schimmel
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=20260208161126.GK154003@shredder \
--to=idosch@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=sdf@fomichev.me \
--cc=shaw.leon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox