diff options
| author | Russell King <[email protected]> | 2020-10-29 16:09:03 +0000 |
|---|---|---|
| committer | Jakub Kicinski <[email protected]> | 2020-10-30 14:31:00 -0700 |
| commit | 1fb74191988fd1cc340c4b2fdaf4c47d2a7d1d17 (patch) | |
| tree | b6f1f422ecea99ce9822ef28e21a2c1a2ea0bb33 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 85bec4bc9198ba233afc830742437847b167b887 (diff) | |
net: dsa: mv88e6xxx: fix vlan setup
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 <[email protected]>
Reviewed-by: Florian Fainelli <[email protected]>
Tested-by: Vladimir Oltean <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions