diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-05-19 18:15:23 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2026-05-19 18:15:24 -0700 |
| commit | 90fc1a393736063b2b4077115e215a2e2eebb797 (patch) | |
| tree | 96b9920fdaad4614491479b14ab95d20f4e54b1f /include | |
| parent | 9b244c242bec48b37e82b89787afd6a4c43457e1 (diff) | |
| parent | ae743a8ca8dbd66fb67c461a27460b2b21c376ab (diff) | |
Merge branch 'bridge-mcast-fix-a-possible-use-after-free-when-removing-a-bridge-port'
Ido Schimmel says:
====================
bridge: mcast: Fix a possible use-after-free when removing a bridge port
Patch #1 fixes a possible use-after-free when removing a bridge port.
Patch #2 adds a test case that triggers the problem.
In net-next we can:
1. Add DEBUG_NET_WARN_ON_ONCE() when a port multicast context is
de-initialized while enabled.
2. When de-initializing a port multicast context, synchronously shutdown
all the timers that were initialized when the context was initialized.
====================
Link: https://patch.msgid.link/20260517121122.188333-1-idosch@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions