linux.git/net/dsa, branch v5.10

net: dsa: tag_ksz: KSZ8795 and KSZ9477 also use tail tags

2020-10-20T00:32:50+00:00

The Marvell 88E6060 uses tag_trailer.c and the KSZ8795, KSZ9477 and
KSZ9893 switches also use tail tags.

Fixes: 7a6ffe764be3 ("net: dsa: point out the tail taggers")
Signed-off-by: Christian Eggers 
Reviewed-by: Florian Fainelli 
Link: https://lore.kernel.org/r/20201016171603.10587-1-ceggers@arri.de
Signed-off-by: Jakub Kicinski

net: dsa: use new function dev_fetch_sw_netstats

2020-10-14T00:33:49+00:00

Simplify the code by using new function dev_fetch_sw_netstats().

Signed-off-by: Heiner Kallweit 
Tested-by: Vladimir Oltean 
Reviewed-by: Florian Fainelli 
Link: https://lore.kernel.org/r/b6047017-8226-6b7e-a3cd-064e69fdfa27@gmail.com
Signed-off-by: Jakub Kicinski

net: dsa: tag_ocelot: use VLAN information from tagging header when available

2020-10-11T18:19:04+00:00

When the Extraction Frame Header contains a valid classified VLAN, use
that instead of the VLAN header present in the packet.

Signed-off-by: Vladimir Oltean 
Signed-off-by: Jakub Kicinski

net: dsa: propagate switchdev vlan_filtering prepare phase to drivers

2020-10-05T12:56:48+00:00

A driver may refuse to enable VLAN filtering for any reason beyond what
the DSA framework cares about, such as:
- having tc-flower rules that rely on the switch being VLAN-aware
- the particular switch does not support VLAN, even if the driver does
  (the DSA framework just checks for the presence of the .port_vlan_add
  and .port_vlan_del pointers)
- simply not supporting this configuration to be toggled at runtime

Currently, when a driver rejects a configuration it cannot support, it
does this from the commit phase, which triggers various warnings in
switchdev.

So propagate the prepare phase to drivers, to give them the ability to
refuse invalid configurations cleanly and avoid the warnings.

Since we need to modify all function prototypes and check for the
prepare phase from within the drivers, take that opportunity and move
the existing driver restrictions within the prepare phase where that is
possible and easy.

Cc: Florian Fainelli 
Cc: Martin Blumenstingl 
Cc: Hauke Mehrtens 
Cc: Woojung Huh 
Cc: Microchip Linux Driver Support 
Cc: Sean Wang 
Cc: Landen Chao 
Cc: Andrew Lunn 
Cc: Vivien Didelot 
Cc: Jonathan McDowell 
Cc: Linus Walleij 
Cc: Alexandre Belloni 
Cc: Claudiu Manoil 
Signed-off-by: Vladimir Oltean 
Signed-off-by: David S. Miller

net: dsa: Add devlink port regions support to DSA

2020-10-04T21:38:53+00:00

Allow DSA drivers to make use of devlink port regions, via simple
wrappers.

Reviewed-by: Vladimir Oltean 
Tested-by: Vladimir Oltean 
Signed-off-by: Andrew Lunn 
Reviewed-by: Florian Fainelli 
Signed-off-by: David S. Miller

net: dsa: Register devlink ports before calling DSA driver setup()

2020-10-04T21:38:53+00:00

DSA drivers want to create regions on devlink ports as well as the
devlink device instance, in order to export registers and other tables
per port. To keep all this code together in the drivers, have the
devlink ports registered early, so the setup() method can setup both
device and port devlink regions.

v3:
Remove dp->setup
Move common code out of switch statement.
Fix wrong goto

Signed-off-by: Andrew Lunn 
Reviewed-by: Florian Fainelli 
Reviewed-by: Vladimir Oltean 
Tested-by: Vladimir Oltean 
Signed-off-by: David S. Miller

net: dsa: Make use of devlink port flavour unused

2020-10-04T21:38:52+00:00

If a port is unused, still create a devlink port for it, but set the
flavour to unused. This allows us to attach devlink regions to the
port, etc.

Reviewed-by: Vladimir Oltean 
Tested-by: Vladimir Oltean 
Signed-off-by: Andrew Lunn 
Reviewed-by: Florian Fainelli 
Signed-off-by: David S. Miller

net: dsa: Utilize __vlan_find_dev_deep_rcu()

2020-10-02T20:36:07+00:00

Now that we are guaranteed that dsa_untag_bridge_pvid() is called after
eth_type_trans() we can utilize __vlan_find_dev_deep_rcu() which will
take care of finding an 802.1Q upper on top of a bridge master.

A common use case, prior to 12a1526d067 ("net: dsa: untag the bridge
pvid from rx skbs") was to configure a bridge 802.1Q upper like this:

ip link add name br0 type bridge vlan_filtering 0
ip link add link br0 name br0.1 type vlan id 1

in order to pop the default_pvid VLAN tag.

With this change we restore that behavior while still allowing the DSA
receive path to automatically pop the VLAN tag.

Signed-off-by: Florian Fainelli 
Reviewed-by: Vladimir Oltean 
Signed-off-by: David S. Miller

net: dsa: Obtain VLAN protocol from skb->protocol

2020-10-02T20:36:07+00:00

Now that dsa_untag_bridge_pvid() is called after eth_type_trans() we are
guaranteed that skb->protocol will be set to a correct value, thus
allowing us to avoid calling vlan_eth_hdr().

Signed-off-by: Florian Fainelli 
Reviewed-by: Vladimir Oltean 
Signed-off-by: David S. Miller

net: dsa: b53: Set untag_bridge_pvid

2020-10-02T20:36:07+00:00

Indicate to the DSA receive path that we need to untage the bridge PVID,
this allows us to remove the dsa_untag_bridge_pvid() calls from
net/dsa/tag_brcm.c.

Signed-off-by: Florian Fainelli 
Reviewed-by: Vladimir Oltean 
Signed-off-by: David S. Miller