diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-10-20 13:04:10 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-10-20 13:04:11 -0700 |
| commit | 2ffc339492fff15ae2479b61247dbb390332a606 (patch) | |
| tree | 906a8eb94e7594472d34b3418812eade7bd5fe5b /rust/kernel/alloc | |
| parent | 38dda0ecd4bb7ac381bcecb81218fc5af80a3ae1 (diff) | |
| parent | 335ae22c2e9db0514fd27615b9bf0c9e2a8302cf (diff) | |
| download | linux-2ffc339492fff15ae2479b61247dbb390332a606.tar.gz linux-2ffc339492fff15ae2479b61247dbb390332a606.zip | |
Merge branch 'bridge-mcast-fix-mdb-exhaustion-by-rejected-entries'
Ido Schimmel says:
====================
bridge: mcast: Fix MDB exhaustion by rejected entries
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.
====================
Link: https://patch.msgid.link/20261016101407.2030133-1-idosch@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'rust/kernel/alloc')
0 files changed, 0 insertions, 0 deletions