1. 04 3月, 2008 1 次提交
  2. 27 2月, 2008 1 次提交
  3. 29 1月, 2008 1 次提交
  4. 01 11月, 2007 1 次提交
  5. 22 10月, 2007 5 次提交
  6. 11 10月, 2007 1 次提交
    • 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
  7. 31 7月, 2007 4 次提交
  8. 24 5月, 2007 1 次提交
  9. 05 5月, 2007 1 次提交
    • M
      [Bluetooth] Fix L2CAP and HCI setsockopt() information leaks · 0878b666
      Marcel Holtmann 提交于
      The L2CAP and HCI setsockopt() implementations have a small information
      leak that makes it possible to leak kernel stack memory to userspace.
      
      If the optlen parameter is 0, no data will be copied by copy_from_user(),
      but the uninitialized stack buffer will be read and stored later. A call
      to getsockopt() can now retrieve the leaked information.
      
      To fix this problem the stack buffer given to copy_from_user() must be
      initialized with the current settings.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      0878b666
  10. 26 4月, 2007 2 次提交
  11. 11 2月, 2007 1 次提交
  12. 23 1月, 2007 2 次提交
  13. 03 12月, 2006 1 次提交
  14. 22 11月, 2006 2 次提交
  15. 16 10月, 2006 2 次提交
  16. 13 7月, 2006 1 次提交
  17. 04 7月, 2006 2 次提交
  18. 01 7月, 2006 1 次提交
  19. 12 1月, 2006 1 次提交
  20. 04 1月, 2006 2 次提交
    • E
      [NET]: move struct proto_ops to const · 90ddc4f0
      Eric Dumazet 提交于
      I noticed that some of 'struct proto_ops' used in the kernel may share
      a cache line used by locks or other heavily modified data. (default
      linker alignement is 32 bytes, and L1_CACHE_LINE is 64 or 128 at
      least)
      
      This patch makes sure a 'struct proto_ops' can be declared as const,
      so that all cpus can share all parts of it without false sharing.
      
      This is not mandatory : a driver can still use a read/write structure
      if it needs to (and eventually a __read_mostly)
      
      I made a global stubstitute to change all existing occurences to make
      them const.
      
      This should reduce the possibility of false sharing on SMP, and
      speedup some socket system calls.
      Signed-off-by: NEric Dumazet <dada1@cosmosbay.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      90ddc4f0
    • B
      [NET]: Avoid atomic xchg() for non-error case · c1cbe4b7
      Benjamin LaHaise 提交于
      It also looks like there were 2 places where the test on sk_err was
      missing from the event wait logic (in sk_stream_wait_connect and
      sk_stream_wait_memory), while the rest of the sock_error() users look
      to be doing the right thing.  This version of the patch fixes those,
      and cleans up a few places that were testing ->sk_err directly.
      Signed-off-by: NBenjamin LaHaise <benjamin.c.lahaise@intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c1cbe4b7
  21. 09 11月, 2005 1 次提交
  22. 09 10月, 2005 1 次提交
  23. 30 8月, 2005 1 次提交
  24. 26 4月, 2005 2 次提交
    • A
      [NET]: kill gratitious includes of major.h · 5523662c
      Al Viro 提交于
      	A lot of places in there are including major.h for no reason
      whatsoever.  Removed.  And yes, it still builds.
      
      	The history of that stuff is often amusing.  E.g. for net/core/sock.c
      the story looks so, as far as I've been able to reconstruct it: we used to
      need major.h in net/socket.c circa 1.1.early.  In 1.1.13 that need had
      disappeared, along with register_chrdev(SOCKET_MAJOR, "socket", &net_fops)
      in sock_init().  Include had not.  When 1.2 -> 1.3 reorg of net/* had moved
      a lot of stuff from net/socket.c to net/core/sock.c, this crap had followed...
      Signed-off-by: NAl Viro <viro@parcelfarce.linux.theplanet.co.uk>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5523662c
    • A
      [PATCH] kill gratitious includes of major.h under net/* · b453257f
      Al Viro 提交于
      A lot of places in there are including major.h for no reason whatsoever.
      Removed.  And yes, it still builds. 
      
      The history of that stuff is often amusing.  E.g.  for net/core/sock.c
      the story looks so, as far as I've been able to reconstruct it: we used
      to need major.h in net/socket.c circa 1.1.early.  In 1.1.13 that need
      had disappeared, along with register_chrdev(SOCKET_MAJOR, "socket",
      &net_fops) in sock_init().  Include had not.  When 1.2 -> 1.3 reorg of
      net/* had moved a lot of stuff from net/socket.c to net/core/sock.c,
      this crap had followed... 
      Signed-off-by: NAl Viro <viro@parcelfarce.linux.theplanet.co.uk>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b453257f
  25. 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