From: Florian Fainelli <florian.fainelli@broadcom.com>
To: "Jonas Gorski" <jonas.gorski@gmail.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Vladimir Oltean" <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
"Vivien Didelot" <vivien.didelot@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: tag_brcm: do not mark link local traffic as offloaded
Date: Mon, 10 Nov 2025 08:04:38 -0800 [thread overview]
Message-ID: <BBB3B106-E173-4098-A90A-3A75C2C545B6@broadcom.com> (raw)
In-Reply-To: <20251109134635.243951-1-jonas.gorski@gmail.com>
On November 9, 2025 5:46:35 AM PST, Jonas Gorski <jonas.gorski@gmail.com> wrote:
>Broadcom switches locally terminate link local traffic and do not
>forward it, so we should not mark it as offloaded.
>
>In some situations we still want/need to flood this traffic, e.g. if STP
>is disabled, or it is explicitly enabled via the group_fwd_mask. But if
>the skb is marked as offloaded, the kernel will assume this was already
>done in hardware, and the packets never reach other bridge ports.
>
>So ensure that link local traffic is never marked as offloaded, so that
>the kernel can forward/flood these packets in software if needed.
>
>Since the local termination in not configurable, check the destination
>MAC, and never mark packets as offloaded if it is a link local ether
>address.
>
>While modern switches set the tag reason code to BRCM_EG_RC_PROT_TERM
>for trapped link local traffic, they also set it for link local traffic
>that is flooded (01:80:c2:00:00:10 to 01:80:c2:00:00:2f), so we cannot
>use it and need to look at the destination address for them as well.
>
>Fixes: 964dbf186eaa ("net: dsa: tag_brcm: add support for legacy tags")
>Fixes: 0e62f543bed0 ("net: dsa: Fix duplicate frames flooded by learning")
>Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
Florian
next prev parent reply other threads:[~2025-11-10 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 13:46 [PATCH net] net: dsa: tag_brcm: do not mark link local traffic as offloaded Jonas Gorski
2025-11-10 11:24 ` Vladimir Oltean
2025-11-10 16:04 ` Florian Fainelli [this message]
2025-11-11 1:20 ` 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=BBB3B106-E173-4098-A90A-3A75C2C545B6@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=horms@kernel.org \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox