diff options
| author | Joseph Huang <[email protected]> | 2025-07-16 15:35:50 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2025-07-17 14:46:41 +0000 |
| commit | 683dc24da8bf199bb7446e445ad7f801c79a550e (patch) | |
| tree | 8d7c303f1a34f7ebeb4517089d80eacf689fb264 /lib/crypto/mpi/mpi-cmp.c | |
| parent | Merge branch 'net-vlan-fix-vlan-0-refcount-imbalance-of-toggling-filtering-du... (diff) | |
| download | kernel-683dc24da8bf199bb7446e445ad7f801c79a550e.tar.gz kernel-683dc24da8bf199bb7446e445ad7f801c79a550e.zip | |
net: bridge: Do not offload IGMP/MLD messages
Do not offload IGMP/MLD messages as it could lead to IGMP/MLD Reports
being unintentionally flooded to Hosts. Instead, let the bridge decide
where to send these IGMP/MLD messages.
Consider the case where the local host is sending out reports in response
to a remote querier like the following:
mcast-listener-process (IP_ADD_MEMBERSHIP)
\
br0
/ \
swp1 swp2
| |
QUERIER SOME-OTHER-HOST
In the above setup, br0 will want to br_forward() reports for
mcast-listener-process's group(s) via swp1 to QUERIER; but since the
source hwdom is 0, the report is eligible for tx offloading, and is
flooded by hardware to both swp1 and swp2, reaching SOME-OTHER-HOST as
well. (Example and illustration provided by Tobias.)
Fixes: 472111920f1c ("net: bridge: switchdev: allow the TX data plane forwarding to be offloaded")
Signed-off-by: Joseph Huang <[email protected]>
Acked-by: Nikolay Aleksandrov <[email protected]>
Reviewed-by: Ido Schimmel <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'lib/crypto/mpi/mpi-cmp.c')
0 files changed, 0 insertions, 0 deletions
