diff options
author | Andrew Lunn <andrew@lunn.ch> | 2017-11-09 22:29:51 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-11-11 19:33:10 +0900 |
commit | a42c8e33f2044d6b56f167b5506c7e09e5b702c2 (patch) | |
tree | fdec8e9144c9bc55923d0328c43f46d2264dd797 /crypto/lrw.c | |
parent | 8c5f9a8c134394ca7cf77f8095e96d4e12177f74 (diff) |
net: dsa: Fix SWITCHDEV_ATTR_ID_PORT_PARENT_ID
SWITCHDEV_ATTR_ID_PORT_PARENT_ID is used by the software bridge when
determining which ports to flood a packet out. If the packet
originated from a switch, it assumes the switch has already flooded
the packet out the switches ports, so the bridge should not flood the
packet itself out switch ports. Ports on the same switch are expected
to return the same parent ID when SWITCHDEV_ATTR_ID_PORT_PARENT_ID is
called.
DSA gets this wrong with clusters of switches. As far as the software
bridge is concerned, the cluster is all one switch. A packet from any
switch in the cluster can be assumed to have been flooded as needed
out of all ports of the cluster, not just the switch it originated
from. Hence all ports of a cluster should return the same parent. The
old implementation did not, each switch in the cluster had its own ID.
Also wrong was that the ID was not unique if multiple DSA instances
are in operation.
Use the tree ID as the parent ID, which is the same for all switches
in a cluster and unique across switch clusters.
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Reviewed-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto/lrw.c')
0 files changed, 0 insertions, 0 deletions