From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org, bridge@lists.linux.dev
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, horms@kernel.org, razor@blackwall.org,
petrm@nvidia.com
Subject: Re: [PATCH net-next v3 1/2] bridge: mcast: Fix a false positive lockdep splat
Date: Thu, 9 Jul 2026 17:08:46 +0300 [thread overview]
Message-ID: <20260709140846.GA1679019@shredder> (raw)
In-Reply-To: <20260708122820.1298718-2-idosch@nvidia.com>
On Wed, Jul 08, 2026 at 03:28:19PM +0300, Ido Schimmel wrote:
> @@ -1783,6 +1841,7 @@ static void __br_multicast_send_query(struct net_bridge_mcast *brmctx,
> u8 sflag,
> bool *need_rexmit)
> {
> + struct sk_buff_head *queue;
> bool over_lmqt = !!sflag;
> struct sk_buff *skb;
> u8 igmp_type;
> @@ -1791,7 +1850,12 @@ static void __br_multicast_send_query(struct net_bridge_mcast *brmctx,
> !br_multicast_ctx_matches_vlan_snooping(brmctx))
> return;
>
> + queue = pmctx ? &pmctx->query_queue : &brmctx->query_queue;
> +
> again_under_lmqt:
> + if (skb_queue_len_lockless(queue) >= BR_MULTICAST_QUERY_QUEUE_LEN_MAX)
> + return;
> +
> skb = br_multicast_alloc_query(brmctx, pmctx, pg, ip_dst, group,
> with_srcs, over_lmqt, sflag, &igmp_type,
> need_rexmit);
> @@ -1800,11 +1864,8 @@ static void __br_multicast_send_query(struct net_bridge_mcast *brmctx,
>
> if (pmctx) {
> skb->dev = pmctx->port->dev;
> - br_multicast_count(brmctx->br, pmctx->port, skb, igmp_type,
> - BR_MCAST_DIR_TX);
> - NF_HOOK(NFPROTO_BRIDGE, NF_BR_LOCAL_OUT,
> - dev_net(pmctx->port->dev), NULL, skb, NULL, skb->dev,
> - br_dev_queue_push_xmit);
> + skb_queue_tail(queue, skb);
> + queue_work(system_highpri_wq, &pmctx->query_queue_work);
The issue reported by sashiko-gemini [1] is addressed in patch #2.
[1]
"This isn't a bug, but it looks like the local variable igmp_type is no
longer used in __br_multicast_send_query.
Since br_multicast_count() was moved out of this function and into the
workqueue processing, the value returned via the &igmp_type parameter
from br_multicast_alloc_query() is no longer read. Could we clean this
up and remove the local variable entirely?"
next prev parent reply other threads:[~2026-07-09 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 12:28 [PATCH net-next v3 0/2] bridge: mcast: Fix a false positive lockdep splat Ido Schimmel
2026-07-08 12:28 ` [PATCH net-next v3 1/2] " Ido Schimmel
2026-07-09 14:08 ` Ido Schimmel [this message]
2026-07-08 12:28 ` [PATCH net-next v3 2/2] bridge: mcast: Remove unnecessary argument from br_multicast_alloc_query() 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=20260709140846.GA1679019@shredder \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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