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@kernel.org, razor@blackwall.org, horms@kernel.org,
petrm@nvidia.com, yunlong_ma@buaa.edu.cn,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net 0/2] bridge: mcast: Fix MDB exhaustion by rejected entries
Date: Fri, 16 Oct 2026 13:14:05 +0300 [thread overview]
Message-ID: <20261016101407.2030133-1-idosch@nvidia.com> (raw)
When the bridge fails to create a port group for a new MDB entry, the
entry is left behind with no ports and is never deleted, but it is still
counted towards mcast_hash_max. Since the introduction of
mcast_max_groups, a host behind a port that reached its maximum can use
this to exhaust the MDB and disable multicast snooping.
Patch #1 fixes the problem by deleting the entry upon failure.
Patch #2 adds a selftest.
Ido Schimmel (2):
bridge: mcast: Delete empty MDB entry when port group creation fails
selftests: forwarding: bridge_mdb_max: Add a test for rejected MDB
entries
net/bridge/br_mdb.c | 16 +-
net/bridge/br_multicast.c | 9 ++
net/bridge/br_private.h | 1 +
.../net/forwarding/bridge_mdb_max.sh | 138 ++++++++++++++++++
4 files changed, 161 insertions(+), 3 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-16 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:14 Ido Schimmel [this message]
2026-10-16 10:14 ` [PATCH net 1/2] bridge: mcast: Delete empty MDB entry when port group creation fails Ido Schimmel
2026-10-16 10:14 ` [PATCH net 2/2] selftests: forwarding: bridge_mdb_max: Add a test for rejected MDB entries Ido Schimmel
2026-10-16 15:51 ` [PATCH net 0/2] bridge: mcast: Fix MDB exhaustion by rejected entries Gabriel Goller
2026-10-20 20:10 ` patchwork-bot+netdevbpf
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=20261016101407.2030133-1-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--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 \
--cc=yunlong_ma@buaa.edu.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.