[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220421230105.3570690-1-vladimir.oltean@nxp.com>
Date: Fri, 22 Apr 2022 02:01:03 +0300
From: Vladimir Oltean <vladimir.oltean@....com>
To: netdev@...r.kernel.org
Cc: Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Paolo Abeni <pabeni@...hat.com>,
Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
Claudiu Manoil <claudiu.manoil@....com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
UNGLinuxDriver@...rochip.com
Subject: [PATCH net 0/2] Fix Ocelot VLAN regressions introduced by FDB isolation
There are 2 regressions in the VLAN handling code of the ocelot/felix
DSA driver which can be seen when running the bridge_vlan_aware.sh
selftest. These manifest in the form of valid VLAN configurations being
rejected by the driver with incorrect extack messages.
First regression occurs when we attempt to install an egress-untagged
bridge VLAN to a bridge port that was brought up *while* it was under a
bridge (not before).
The second regression occurs when a port leaves a VLAN-aware bridge and
then re-joins it.
Both issues can be traced back to the recent commit which added VLAN
based FDB isolation in the ocelot driver.
Vladimir Oltean (2):
net: mscc: ocelot: ignore VID 0 added by 8021q module
net: mscc: ocelot: don't add VID 0 to ocelot->vlans when leaving
VLAN-aware bridge
drivers/net/ethernet/mscc/ocelot.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
--
2.25.1
Powered by blists - more mailing lists