1. 12 7月, 2007 2 次提交
    • P
      [RTNETLINK]: rtnl_link API simplification · 2d85cba2
      Patrick McHardy 提交于
      All drivers need to unregister their devices in the module unload function.
      While doing so they must hold the rtnl and atomically unregister the
      rtnl_link ops as well. This makes the rtnl_link_unregister function that
      takes the rtnl itself completely useless.
      
      Provide default newlink/dellink functions, make __rtnl_link_unregister and
      rtnl_link_unregister unregister all devices with matching rtnl_link_ops and
      change the existing users to take advantage of that.
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2d85cba2
    • P
      [VLAN]: Fix MAC address handling · 8c979c26
      Patrick McHardy 提交于
      The VLAN MAC address handling is broken in multiple ways. When the address
      differs when setting it, the real device is put in promiscous mode twice,
      but never taken out again. Additionally it doesn't resync when the real
      device's address is changed and needlessly puts it in promiscous mode when
      the vlan device is still down.
      
      Fix by moving address handling to vlan_dev_open/vlan_dev_stop and properly
      deal with address changes in the device notifier. Also switch to
      dev_unicast_add (which needs the exact same handling).
      
      Since the set_mac_address handler is identical to the generic ethernet one
      with these changes, kill it and use ether_setup().
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8c979c26
  2. 11 7月, 2007 8 次提交
  3. 04 6月, 2007 1 次提交
  4. 03 6月, 2007 1 次提交
  5. 04 5月, 2007 1 次提交
  6. 26 4月, 2007 1 次提交
  7. 03 3月, 2007 1 次提交
  8. 11 2月, 2007 1 次提交
  9. 25 7月, 2006 1 次提交
  10. 22 7月, 2006 1 次提交
  11. 04 7月, 2006 1 次提交
  12. 21 3月, 2006 1 次提交
  13. 12 1月, 2006 1 次提交
  14. 22 12月, 2005 1 次提交
  15. 13 7月, 2005 1 次提交
    • T
      [VLAN]: Fix early vlan adding leads to not functional device · f4637b55
      Tommy Christensen 提交于
      OK, I can see what's happening here. eth0 doesn't detect link-up until
      after a few seconds, so when the vlan interface is opened immediately
      after eth0 has been opened, it inherits the link-down state. Subsequently
      the vlan interface is never properly activated and are thus unable to
      transmit any packets.
      
      dev->state bits are not supposed to be manipulated directly. Something
      similar is probably needed for the netif_device_present() bit, although
      I don't know how this is meant to work for a virtual device.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f4637b55
  16. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4