net: bridge: Do not offload IGMP/MLD messages
authorJoseph Huang <Joseph.Huang@garmin.com>
Wed, 16 Jul 2025 15:35:50 +0000 (11:35 -0400)
committerJakub Kicinski <kuba@kernel.org>
Thu, 17 Jul 2025 14:46:41 +0000 (07:46 -0700)
commit683dc24da8bf199bb7446e445ad7f801c79a550e
tree8d7c303f1a34f7ebeb4517089d80eacf689fb264
parent9bb8a9f6ea964e25b2a2a6e464bad85ea591b230
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 <Joseph.Huang@garmin.com>
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
Link: https://patch.msgid.link/20250716153551.1830255-1-Joseph.Huang@garmin.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
net/bridge/br_switchdev.c