net: switchdev: do not propagate bridge updates across bridges
authorRussell King <rmk+kernel@armlinux.org.uk>
Wed, 26 Feb 2020 17:14:21 +0000 (17:14 +0000)
committerDavid S. Miller <davem@davemloft.net>
Thu, 27 Feb 2020 04:58:33 +0000 (20:58 -0800)
commit07c6f9805f12f1bb538ef165a092b300350384aa
tree664ea887d59db5da6134079f3a424a7078485a5a
parent9baeea50718fdd55c7ae4d61c15f2a71aef6e050
net: switchdev: do not propagate bridge updates across bridges

When configuring a tree of independent bridges, propagating changes
from the upper bridge across a bridge master to the lower bridge
ports brings surprises.

For example, a lower bridge may have vlan filtering enabled.  It
may have a vlan interface attached to the bridge master, which may
then be incorporated into another bridge.  As soon as the lower
bridge vlan interface is attached to the upper bridge, the lower
bridge has vlan filtering disabled.

This occurs because switchdev recursively applies its changes to
all lower devices no matter what.

Reviewed-by: Ido Schimmel <idosch@mellanox.com>
Tested-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/switchdev/switchdev.c