Ethernet Bridge development
 help / color / mirror / Atom feed
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, Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next v3 0/2] bridge: mcast: Fix a false positive lockdep splat
Date: Wed,  8 Jul 2026 15:28:18 +0300	[thread overview]
Message-ID: <20260708122820.1298718-1-idosch@nvidia.com> (raw)

Patch #1 fixes false positive lockdep splat. See the commit message for
more details.

Patch #2 is small cleanup following the previous patch.

Targeting at net-next since this is a false positive that is only
visible with lockdep enabled and the change is not small / trivial.

v3:
  - Use skb_queue_splice_tail_init() (Eric).
  - Increment multicast stats from the workqueue.
  - Add patch #2.
  - Target at net-next.

v2: https://lore.kernel.org/netdev/20260430162604.1043756-1-idosch@nvidia.com/
  - Limit the queue to 1,000 skbs.
  - Edit the trace to avoid checkpatch errors.

v1: https://lore.kernel.org/netdev/20260426133435.207006-1-idosch@nvidia.com/

Ido Schimmel (2):
  bridge: mcast: Fix a false positive lockdep splat
  bridge: mcast: Remove unnecessary argument from
    br_multicast_alloc_query()

 net/bridge/br_multicast.c | 105 ++++++++++++++++++++++++++++++--------
 net/bridge/br_private.h   |   4 ++
 2 files changed, 89 insertions(+), 20 deletions(-)

-- 
2.54.0


             reply	other threads:[~2026-07-08 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 12:28 Ido Schimmel [this message]
2026-07-08 12:28 ` [PATCH net-next v3 1/2] bridge: mcast: Fix a false positive lockdep splat Ido Schimmel
2026-07-09 14:08   ` Ido Schimmel
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=20260708122820.1298718-1-idosch@nvidia.com \
    --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