1. 11 12月, 2007 1 次提交
  2. 07 12月, 2007 1 次提交
  3. 11 11月, 2007 2 次提交
  4. 07 11月, 2007 1 次提交
    • P
      [VLAN]: Fix SET_VLAN_INGRESS_PRIORITY_CMD ioctl · fffe470a
      Patrick McHardy 提交于
      Based on report and patch by Doug Kehn <rdkehn@yahoo.com>:
      
      vconfig returns the following error when attempting to execute the
      set_ingress_map command:
      
      vconfig: socket or ioctl error for set_ingress_map: Operation not permitted
      
      In vlan.c, vlan_ioctl_handler for SET_VLAN_INGRESS_PRIORITY_CMD
      sets err = -EPERM and calls vlan_dev_set_ingress_priority.
      vlan_dev_set_ingress_priority is a void function so err remains
      at -EPERM and results in the vconfig error (even though the ingress
      map was set).
      
      Fix by setting err = 0 after the vlan_dev_set_ingress_priority call.
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      fffe470a
  5. 11 10月, 2007 5 次提交
    • U
      [8021Q]: transfer dev_id from real device · 3607c446
      Ursula Braun 提交于
      A net_device struct provides field dev_id. It is used for
      unique ipv6 generation in case of shared network cards
      (as for the OSA network cards of IBM System z).
      If VLAN devices are built on top of such shared network cards,
      this dev_id information needs to be transferred to the VLAN device.
      Signed-off-by: NUrsula Braun <braunu@de.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3607c446
    • S
      [NET]: Move hardware header operations out of netdevice. · 3b04ddde
      Stephen Hemminger 提交于
      Since hardware header operations are part of the protocol class
      not the device instance, make them into a separate object and
      save memory.
      Signed-off-by: NStephen Hemminger <shemminger@linux-foundation.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3b04ddde
    • R
      [NET]: Nuke SET_MODULE_OWNER macro. · 10d024c1
      Ralf Baechle 提交于
      It's been a useless no-op for long enough in 2.6 so I figured it's time to
      remove it.  The number of people that could object because they're
      maintaining unified 2.4 and 2.6 drivers is probably rather small.
      
      [ Handled drivers added by netdev tree and some missed IRDA cases... -DaveM ]
      Signed-off-by: NRalf Baechle <ralf@linux-mips.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      10d024c1
    • E
      [NET]: Make the device list and device lookups per namespace. · 881d966b
      Eric W. Biederman 提交于
      This patch makes most of the generic device layer network
      namespace safe.  This patch makes dev_base_head a
      network namespace variable, and then it picks up
      a few associated variables.  The functions:
      dev_getbyhwaddr
      dev_getfirsthwbytype
      dev_get_by_flags
      dev_get_by_name
      __dev_get_by_name
      dev_get_by_index
      __dev_get_by_index
      dev_ioctl
      dev_ethtool
      dev_load
      wireless_process_ioctl
      
      were modified to take a network namespace argument, and
      deal with it.
      
      vlan_ioctl_set and brioctl_set were modified so their
      hooks will receive a network namespace argument.
      
      So basically anthing in the core of the network stack that was
      affected to by the change of dev_base was modified to handle
      multiple network namespaces.  The rest of the network stack was
      simply modified to explicitly use &init_net the initial network
      namespace.  This can be fixed when those components of the network
      stack are modified to handle multiple network namespaces.
      
      For now the ifindex generator is left global.
      
      Fundametally ifindex numbers are per namespace, or else
      we will have corner case problems with migration when
      we get that far.
      
      At the same time there are assumptions in the network stack
      that the ifindex of a network device won't change.  Making
      the ifindex number global seems a good compromise until
      the network stack can cope with ifindex changes when
      you change namespaces, and the like.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      881d966b
    • E
      [NET]: Make device event notification network namespace safe · e9dc8653
      Eric W. Biederman 提交于
      Every user of the network device notifiers is either a protocol
      stack or a pseudo device.  If a protocol stack that does not have
      support for multiple network namespaces receives an event for a
      device that is not in the initial network namespace it quite possibly
      can get confused and do the wrong thing.
      
      To avoid problems until all of the protocol stacks are converted
      this patch modifies all netdev event handlers to ignore events on
      devices that are not in the initial network namespace.
      
      As the rest of the code is made network namespace aware these
      checks can be removed.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e9dc8653
  6. 17 9月, 2007 1 次提交
  7. 25 7月, 2007 1 次提交
  8. 15 7月, 2007 2 次提交
  9. 12 7月, 2007 3 次提交
    • P
      [RTNETLINK]: rtnl_link: allow specifying initial device address · 0e06877c
      Patrick McHardy 提交于
      Drivers need to validate the initial addresses in their netlink attribute
      validation function or manually reject them if they can't support this.
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0e06877c
    • 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
  10. 11 7月, 2007 8 次提交
  11. 04 6月, 2007 1 次提交
  12. 03 6月, 2007 1 次提交
  13. 04 5月, 2007 1 次提交
  14. 26 4月, 2007 1 次提交
  15. 03 3月, 2007 1 次提交
  16. 11 2月, 2007 1 次提交
  17. 25 7月, 2006 1 次提交
  18. 22 7月, 2006 1 次提交
  19. 04 7月, 2006 1 次提交
  20. 21 3月, 2006 1 次提交
  21. 12 1月, 2006 1 次提交
  22. 22 12月, 2005 1 次提交
  23. 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
  24. 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