1. 15 2月, 2018 1 次提交
  2. 14 12月, 2017 1 次提交
  3. 08 12月, 2017 1 次提交
  4. 07 12月, 2017 1 次提交
  5. 11 11月, 2017 1 次提交
    • A
      net: dsa: Fix SWITCHDEV_ATTR_ID_PORT_PARENT_ID · a42c8e33
      Andrew Lunn 提交于
      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: NAndrew Lunn <andrew@lunn.ch>
      Reviewed-by: NVivien Didelot <vivien.didelot@savoirfairelinux.com>
      Reviewed-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a42c8e33
  6. 10 11月, 2017 1 次提交
  7. 09 11月, 2017 1 次提交
  8. 05 11月, 2017 1 次提交
  9. 02 11月, 2017 1 次提交
  10. 01 11月, 2017 1 次提交
  11. 27 10月, 2017 1 次提交
  12. 21 10月, 2017 2 次提交
  13. 18 10月, 2017 5 次提交
  14. 13 10月, 2017 1 次提交
  15. 01 10月, 2017 1 次提交
  16. 29 9月, 2017 1 次提交
    • F
      net: dsa: Fix network device registration order · e804441c
      Florian Fainelli 提交于
      We cannot be registering the network device first, then setting its
      carrier off and finally connecting it to a PHY, doing that leaves a
      window during which the carrier is at best inconsistent, and at worse
      the device is not usable without a down/up sequence since the network
      device is visible to user space with possibly no PHY device attached.
      
      Re-order steps so that they make logical sense. This fixes some devices
      where the port was not usable after e.g: an unbind then bind of the
      driver.
      
      Fixes: 0071f56e ("dsa: Register netdev before phy")
      Fixes: 91da11f8 ("net: Distributed Switch Architecture protocol support")
      Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e804441c
  17. 27 9月, 2017 5 次提交
  18. 26 9月, 2017 2 次提交
  19. 22 9月, 2017 2 次提交
  20. 21 9月, 2017 1 次提交
  21. 20 9月, 2017 2 次提交
  22. 06 9月, 2017 1 次提交
  23. 12 8月, 2017 1 次提交
  24. 08 8月, 2017 5 次提交