1. 27 12月, 2009 1 次提交
    • O
      llc: convert the socket list to RCU locking · b76f5a84
      Octavian Purdila 提交于
      For the reclamation phase we use the SLAB_DESTROY_BY_RCU mechanism,
      which require some extra checks in the lookup code:
      
      a) If the current socket was released, reallocated & inserted in
      another list it will short circuit the iteration for the current list,
      thus we need to restart the lookup.
      
      b) If the current socket was released, reallocated & inserted in the
      same list we just need to recheck it matches the look-up criteria and
      if not we can skip to the next element.
      
      In this case there is no need to restart the lookup, since sockets are
      inserted at the start of the list and the worst that will happen is
      that we will iterate throught some of the list elements more then
      once.
      
      Note that the /proc and multicast delivery was not yet converted to
      RCU, it still uses spinlocks for protection.
      Signed-off-by: NOctavian Purdila <opurdila@ixiacom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b76f5a84
  2. 30 5月, 2008 1 次提交
  3. 01 4月, 2008 1 次提交
  4. 26 4月, 2007 3 次提交
  5. 11 2月, 2007 1 次提交
  6. 14 8月, 2006 1 次提交
  7. 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
  8. 18 6月, 2006 1 次提交
  9. 22 9月, 2005 4 次提交
  10. 30 8月, 2005 1 次提交
  11. 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