1. 06 11月, 2009 1 次提交
  2. 07 10月, 2009 1 次提交
  3. 01 10月, 2009 1 次提交
  4. 07 8月, 2009 1 次提交
  5. 13 7月, 2009 1 次提交
  6. 24 6月, 2009 1 次提交
    • H
      net: Move rx skb_orphan call to where needed · d55d87fd
      Herbert Xu 提交于
      In order to get the tun driver to account packets, we need to be
      able to receive packets with destructors set.  To be on the safe
      side, I added an skb_orphan call for all protocols by default since
      some of them (IP in particular) cannot handle receiving packets
      destructors properly.
      
      Now it seems that at least one protocol (CAN) expects to be able
      to pass skb->sk through the rx path without getting clobbered.
      
      So this patch attempts to fix this properly by moving the skb_orphan
      call to where it's actually needed.  In particular, I've added it
      to skb_set_owner_[rw] which is what most users of skb->destructor
      call.
      
      This is actually an improvement for tun too since it means that
      we only give back the amount charged to the socket when the skb
      is passed to another socket that will also be charged accordingly.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Tested-by: NOliver Hartkopp <olver@hartkopp.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d55d87fd
  7. 18 6月, 2009 1 次提交
  8. 04 6月, 2008 1 次提交
  9. 26 3月, 2008 1 次提交
  10. 06 3月, 2008 1 次提交
  11. 29 1月, 2008 1 次提交
  12. 21 1月, 2008 1 次提交
  13. 09 1月, 2008 1 次提交
  14. 01 11月, 2007 1 次提交
  15. 11 10月, 2007 2 次提交
    • 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
    • S
      bcb5e0ee
  16. 18 7月, 2007 1 次提交
    • S
      [IrDA]: Fix IrDA build failure · 75a69ac6
      Samuel Ortiz 提交于
      When having built-in IrDA, we hit the following error:
      
      `irda_sysctl_unregister' referenced in section `.init.text' of
      net/built-in.o: defined in discarded section `.exit.text' of
      net/built-in.o
      `irda_proc_unregister' referenced in section `.init.text' of
      net/built-in.o: defined in discarded section `.exit.text' of
      net/built-in.o
      `irsock_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      `irttp_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      `iriap_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      `irda_device_cleanup' referenced in section `.init.text' of
      net/built-in.o: defined in discarded section `.exit.text' of
      net/built-in.o
      `irlap_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      `irlmp_cleanup' referenced in section `.init.text' of net/built-in.o:
      defined in discarded section `.exit.text' of net/built-in.o
      make[1]: *** [.tmp_vmlinux1] Error 1
      make: *** [_all] Error 2
      
      This is due to the irda_init fix recently added, where we call __exit
      routines from an __init one. It is a build failure that I didn't catch
      because it doesn't show up when building IrDA as a module. My apologies
      for that.
      The following patch fixes that failure and is against your net-2.6
      tree. I hope it can make it to the merge window, and stable@kernel.org
      is CCed on this mail.
      Signed-off-by: NSamuel Ortiz <samuel@sortiz.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      75a69ac6
  17. 09 5月, 2007 1 次提交
  18. 26 4月, 2007 7 次提交
  19. 19 4月, 2007 1 次提交
    • O
      [IrDA]: Correctly handling socket error · bfb6709d
      Olaf Kirch 提交于
      This patch fixes an oops first reported in mid 2006 - see
      http://lkml.org/lkml/2006/8/29/358 The cause of this bug report is that
      when an error is signalled on the socket, irda_recvmsg_stream returns
      without removing a local wait_queue variable from the socket's sk_sleep
      queue. This causes havoc further down the road.
      
      In response to this problem, a patch was made that invoked sock_orphan on
      the socket when receiving a disconnect indication. This is not a good fix,
      as this sets sk_sleep to NULL, causing applications sleeping in recvmsg
      (and other places) to oops.
      
      This is against the latest net-2.6 and should be considered for -stable
      inclusion. 
      Signed-off-by: NOlaf Kirch <olaf.kirch@oracle.com>
      Signed-off-by: NSamuel Ortiz <samuel@sortiz.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bfb6709d
  20. 11 2月, 2007 1 次提交
  21. 29 9月, 2006 2 次提交
  22. 22 7月, 2006 1 次提交
  23. 01 7月, 2006 1 次提交
  24. 29 3月, 2006 2 次提交
  25. 12 1月, 2006 1 次提交
  26. 04 1月, 2006 3 次提交
  27. 30 8月, 2005 1 次提交
  28. 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