1. 23 2月, 2009 1 次提交
  2. 22 11月, 2008 1 次提交
  3. 17 6月, 2008 1 次提交
  4. 28 3月, 2008 1 次提交
  5. 06 3月, 2008 1 次提交
  6. 20 10月, 2007 1 次提交
  7. 11 10月, 2007 2 次提交
    • 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 socket creation namespace safe. · 1b8d7ae4
      Eric W. Biederman 提交于
      This patch passes in the namespace a new socket should be created in
      and has the socket code do the appropriate reference counting.  By
      virtue of this all socket create methods are touched.  In addition
      the socket create methods are modified so that they will fail if
      you attempt to create a socket in a non-default network namespace.
      
      Failing if we attempt to create a socket outside of the default
      network namespace ensures that as we incrementally make the network stack
      network namespace aware we will not export functionality that someone
      has not audited and made certain is network namespace safe.
      Allowing us to partially enable network namespaces before all of the
      exotic protocols are supported.
      
      Any protocol layers I have missed will fail to compile because I now
      pass an extra parameter into the socket creation code.
      
      [ Integrated AF_IUCV build fixes from Andrew Morton... -DaveM ]
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1b8d7ae4
  8. 09 5月, 2007 1 次提交
  9. 11 2月, 2007 1 次提交
  10. 03 12月, 2006 1 次提交
  11. 05 8月, 2006 1 次提交
    • S
      [LLX]: SOCK_DGRAM interface fixes · 30a584d9
      Stephen Hemminger 提交于
      The datagram interface of LLC is broken in a couple of ways.
      These were discovered when trying to use it to build an out-of-kernel
      version of STP.
      
      First it didn't pass the source address of the received packet
      in recvfrom(). It needs to copy the source address of received LLC packets
      into the socket control block. At the same time fix a security issue
      because there was uninitialized data leakage. Every recvfrom call
      was just copying out old data.
      
      Second, LLC should not merge multiple packets in one receive call
      on datagram sockets. LLC should preserve packet boundaries on
      SOCK_DGRAM.
      
      This fix goes against the old historical comments about UNIX98 semantics
      but without this fix SOCK_DGRAM is broken and useless. So either ANK's
      interpretation was incorect or UNIX98 standard was wrong.
      Signed-off-by: NStephen Hemminger <shemminger@osdl.org>
      Acked-by: NArnaldo Carvalho de Melo <acme@mandriva.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      30a584d9
  12. 01 7月, 2006 1 次提交
  13. 18 6月, 2006 2 次提交
  14. 21 3月, 2006 3 次提交
  15. 04 1月, 2006 3 次提交
  16. 15 11月, 2005 1 次提交
  17. 22 9月, 2005 14 次提交
  18. 30 8月, 2005 2 次提交
  19. 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