1. 12 6月, 2008 1 次提交
  2. 22 5月, 2008 1 次提交
  3. 16 4月, 2008 7 次提交
  4. 06 3月, 2008 2 次提交
  5. 05 3月, 2008 1 次提交
  6. 27 2月, 2008 1 次提交
    • P
      [INET]: Don't create tunnels with '%' in name. · b37d428b
      Pavel Emelyanov 提交于
      Four tunnel drivers (ip_gre, ipip, ip6_tunnel and sit) can receive a
      pre-defined name for a device from the userspace.  Since these drivers
      call the register_netdevice() (rtnl_lock, is held), which does _not_
      generate the device's name, this name may contain a '%' character.
      
      Not sure how bad is this to have a device with a '%' in its name, but
      all the other places either use the register_netdev(), which call the
      dev_alloc_name(), or explicitly call the dev_alloc_name() before
      registering, i.e. do not allow for such names.
      
      This had to be prior to the commit 34cc7b, but I forgot to number the
      patches and this one got lost, sorry.
      Signed-off-by: NPavel Emelyanov <xemul@openvz.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b37d428b
  7. 24 2月, 2008 1 次提交
  8. 19 2月, 2008 1 次提交
  9. 29 1月, 2008 4 次提交
  10. 24 10月, 2007 1 次提交
  11. 11 10月, 2007 2 次提交
    • 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
  12. 27 7月, 2007 1 次提交
    • A
      ip6_tunnel - endianness annotations · 704eae1f
      Al Viro 提交于
      Convert rel_info to host-endian before calling ip6_tnl_err().
      The things become much more straightforward that way.
      The key observation (and the reason why that code actually
      worked) is that after ip6_tnl_err() we either immediately
      bailed out or had rel_info set to 0 or had it set to host-endian
      and guaranteed to hit
      (rel_type == ICMP_DEST_UNREACH && rel_code == ICMP_FRAG_NEEDED)
      case.  So inconsistent endianness didn't really lead to bugs,
      but it had been subtle and prone to breakage.  New variant is
      saner and obviously safe.
      Signed-off-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      704eae1f
  13. 22 7月, 2007 1 次提交
  14. 11 7月, 2007 1 次提交
  15. 26 4月, 2007 12 次提交
  16. 27 2月, 2007 1 次提交
  17. 14 2月, 2007 1 次提交
  18. 11 2月, 2007 1 次提交