From: Simon Horman <horms@kernel.org>
To: Jonas Gorski <jonas.gorski@gmail.com>
Cc: "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>,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: tag_brcm: legacy: fix untagged rx on unbridged ports for bcm63xx
Date: Wed, 15 Oct 2025 17:12:27 +0100 [thread overview]
Message-ID: <aO_H6187Oahh24IX@horms.kernel.org> (raw)
In-Reply-To: <20251015070854.36281-1-jonas.gorski@gmail.com>
On Wed, Oct 15, 2025 at 09:08:54AM +0200, Jonas Gorski wrote:
> The internal switch on BCM63XX SoCs will unconditionally add 802.1Q VLAN
> tags on egress to CPU when 802.1Q mode is enabled. We do this
> unconditionally since commit ed409f3bbaa5 ("net: dsa: b53: Configure
> VLANs while not filtering").
>
> This is fine for VLAN aware bridges, but for standalone ports and vlan
> unaware bridges this means all packets are tagged with the default VID,
> which is 0.
>
> While the kernel will treat that like untagged, this can break userspace
> applications processing raw packets, expecting untagged traffic, like
> STP daemons.
>
> This also breaks several bridge tests, where the tcpdump output then
> does not match the expected output anymore.
>
> Since 0 isn't a valid VID, just strip out the VLAN tag if we encounter
> it, unless the priority field is set, since that would be a valid tag
> again.
>
> Fixes: 964dbf186eaa ("net: dsa: tag_brcm: add support for legacy tags")
> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
...
> @@ -237,8 +239,14 @@ static struct sk_buff *brcm_leg_tag_rcv(struct sk_buff *skb,
> if (!skb->dev)
> return NULL;
>
> - /* VLAN tag is added by BCM63xx internal switch */
> - if (netdev_uses_dsa(skb->dev))
> + /* The internal switch in BCM63XX SoCs will add a 802.1Q VLAN tag on
> + * egress to the CPU port for all packets, regardless of the untag bit
> + * in the VLAN table. VID 0 is used for untagged traffic on unbridged
> + * ports and vlan unaware bridges. If we encounter a VID 0 tagged
> + * packet, we know it is supposed to be untagged, so strip the VLAN
> + * tag as well in that case.
Maybe it isn't important, but here it is a TCI 0 that is being checked:
VID 0, PCP 0, and DEI 0.
> + */
> + if (proto[0] == htons(ETH_P_8021Q) && proto[1] == 0)
> len += VLAN_HLEN;
>
> /* Remove Broadcom tag and update checksum */
>
> base-commit: 7f0fddd817ba6daebea1445ae9fab4b6d2294fa8
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-10-15 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 7:08 [PATCH net] net: dsa: tag_brcm: legacy: fix untagged rx on unbridged ports for bcm63xx Jonas Gorski
2025-10-15 16:12 ` Simon Horman [this message]
2025-10-15 16:24 ` Jonas Gorski
2025-10-15 16:43 ` Simon Horman
2025-10-21 9:38 ` Jonas Gorski
2025-10-16 10:27 ` Vladimir Oltean
2025-10-16 11:50 ` Jonas Gorski
2025-10-21 7:08 ` Paolo Abeni
2025-10-21 7:30 ` Jonas Gorski
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=aO_H6187Oahh24IX@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).