[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201030143147.3ad112dc@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Fri, 30 Oct 2020 14:31:47 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Russell King <rmk+kernel@...linux.org.uk>
Cc: Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>
Subject: Re: [PATCH net-next] net: dsa: mv88e6xxx: fix vlan setup
On Thu, 29 Oct 2020 16:09:03 +0000 Russell King wrote:
> DSA assumes that a bridge which has vlan filtering disabled is not
> vlan aware, and ignores all vlan configuration. However, the kernel
> software bridge code allows configuration in this state.
>
> This causes the kernel's idea of the bridge vlan state and the
> hardware state to disagree, so "bridge vlan show" indicates a correct
> configuration but the hardware lacks all configuration. Even worse,
> enabling vlan filtering on a DSA bridge immediately blocks all traffic
> which, given the output of "bridge vlan show", is very confusing.
>
> Allow the VLAN configuration to be updated on Marvell DSA bridges,
> otherwise we end up cutting all traffic when enabling vlan filtering.
>
> Signed-off-by: Russell King <rmk+kernel@...linux.org.uk>
Applied, thanks!
Powered by blists - more mailing lists