1. 29 1月, 2008 3 次提交
    • H
      [IPSEC]: Store xfrm states in security path directly · b2aa5e9d
      Herbert Xu 提交于
      As it is xfrm_input first collects a list of xfrm states on the stack
      before storing them in the packet's security path just before it
      returns.  For async crypto, this construction presents an obstacle
      since we may need to leave the loop after each transform.
      
      In fact, it's much easier to just skip the stack completely and always
      store to the security path.  This is proven by the fact that this
      patch actually shrinks the code.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b2aa5e9d
    • H
      [IPSEC]: Merge most of the input path · 716062fd
      Herbert Xu 提交于
      As part of the work on asynchronous cryptographic operations, we need
      to be able to resume from the spot where they occur.  As such, it
      helps if we isolate them to one spot.
      
      This patch moves most of the remaining family-specific processing into
      the common input code.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      716062fd
    • H
      [IPSEC]: Separate inner/outer mode processing on input · 227620e2
      Herbert Xu 提交于
      With inter-family transforms the inner mode differs from the outer
      mode.  Attempting to handle both sides from the same function means
      that it needs to handle both IPv4 and IPv6 which creates duplication
      and confusion.
      
      This patch separates the two parts on the input path so that each
      function deals with one family only.
      
      In particular, the functions xfrm4_extract_inut/xfrm6_extract_inut
      moves the pertinent fields from the IPv4/IPv6 IP headers into a
      neutral format stored in skb->cb.  This is then used by the inner mode
      input functions to modify the inner IP header.  In this way the input
      function no longer has to know about the outer address family.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      227620e2
  2. 18 10月, 2007 1 次提交
  3. 20 7月, 2007 1 次提交
    • P
      mm: Remove slab destructors from kmem_cache_create(). · 20c2df83
      Paul Mundt 提交于
      Slab destructors were no longer supported after Christoph's
      c59def9f change. They've been
      BUGs for both slab and slub, and slob never supported them
      either.
      
      This rips out support for the dtor pointer from kmem_cache_create()
      completely and fixes up every single callsite in the kernel (there were
      about 224, not including the slab allocator definitions themselves,
      or the documentation references).
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      20c2df83
  4. 26 4月, 2007 1 次提交
  5. 11 2月, 2007 1 次提交
  6. 08 12月, 2006 2 次提交
  7. 29 9月, 2006 1 次提交
  8. 23 9月, 2006 1 次提交
  9. 23 5月, 2006 1 次提交
  10. 01 4月, 2006 1 次提交
  11. 30 8月, 2005 1 次提交
  12. 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