1. 23 6月, 2009 1 次提交
  2. 15 12月, 2008 1 次提交
  3. 25 3月, 2008 1 次提交
  4. 01 2月, 2008 1 次提交
  5. 18 10月, 2007 2 次提交
  6. 11 10月, 2007 3 次提交
  7. 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
  8. 11 7月, 2007 1 次提交
  9. 29 4月, 2007 1 次提交
  10. 26 4月, 2007 1 次提交
  11. 23 3月, 2007 1 次提交
  12. 14 2月, 2007 1 次提交
  13. 11 2月, 2007 1 次提交
  14. 08 12月, 2006 2 次提交
  15. 03 12月, 2006 2 次提交
  16. 02 11月, 2006 1 次提交
  17. 29 9月, 2006 1 次提交
  18. 23 9月, 2006 1 次提交
  19. 25 7月, 2006 1 次提交
    • D
      [IPV6] xfrm6_tunnel: Delete debugging code. · a922ba55
      David S. Miller 提交于
      It doesn't compile, and it's dubious in several regards:
      
      1) is enabled by non-Kconfig controlled CONFIG_* value
         (noted by Randy Dunlap)
      2) XFRM6_TUNNEL_SPI_MAGIC is defined after it's first use
      3) the debugging messages print object pointer addresses
         which have no meaning without context
      
      So let's just get rid of it.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a922ba55
  20. 01 7月, 2006 1 次提交
  21. 01 4月, 2006 1 次提交
    • H
      [IPSEC]: Kill unused decap state argument · e695633e
      Herbert Xu 提交于
      This patch removes the decap_state argument from the xfrm input hook.
      Previously this function allowed the input hook to share state with
      the post_input hook.  The latter has since been removed.
      
      The only purpose for it now is to check the encap type.  However, it
      is easier and better to move the encap type check to the generic
      xfrm_rcv function.  This allows us to get rid of the decap state
      argument altogether.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e695633e
  22. 29 3月, 2006 1 次提交
    • H
      [INET]: Introduce tunnel4/tunnel6 · d2acc347
      Herbert Xu 提交于
      Basically this patch moves the generic tunnel protocol stuff out of
      xfrm4_tunnel/xfrm6_tunnel and moves it into the new files of tunnel4.c
      and tunnel6 respectively.
      
      The reason for this is that the problem that Hugo uncovered is only
      the tip of the iceberg.  The real problem is that when we removed the
      dependency of ipip on xfrm4_tunnel we didn't really consider the module
      case at all.
      
      For instance, as it is it's possible to build both ipip and xfrm4_tunnel
      as modules and if the latter is loaded then ipip simply won't load.
      
      After considering the alternatives I've decided that the best way out of
      this is to restore the dependency of ipip on the non-xfrm-specific part
      of xfrm4_tunnel.  This is acceptable IMHO because the intention of the
      removal was really to be able to use ipip without the xfrm subsystem.
      This is still preserved by this patch.
      
      So now both ipip/xfrm4_tunnel depend on the new tunnel4.c which handles
      the arbitration between the two.  The order of processing is determined
      by a simple integer which ensures that ipip gets processed before
      xfrm4_tunnel.
      
      The situation for ICMP handling is a little bit more complicated since
      we may not have enough information to determine who it's for.  It's not
      a big deal at the moment since the xfrm ICMP handlers are basically
      no-ops.  In future we can deal with this when we look at ICMP caching
      in general.
      
      The user-visible change to this is the removal of the TUNNEL Kconfig
      prompts.  This makes sense because it can only be used through IPCOMP
      as it stands.
      
      The addition of the new modules shouldn't introduce any problems since
      module dependency will cause them to be loaded.
      
      Oh and I also turned some unnecessary pskb's in IPv6 related to this
      patch to skb's.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d2acc347
  23. 21 3月, 2006 1 次提交
  24. 14 1月, 2006 1 次提交
    • J
      [NET]: Use NIP6_FMT in kernel.h · 46b86a2d
      Joe Perches 提交于
      There are errors and inconsistency in the display of NIP6 strings.
      	ie: net/ipv6/ip6_flowlabel.c
      
      There are errors and inconsistency in the display of NIPQUAD strings too.
      	ie: net/netfilter/nf_conntrack_ftp.c
      
      This patch:
      	adds NIP6_FMT to kernel.h
      	changes all code to use NIP6_FMT
      	fixes net/ipv6/ip6_flowlabel.c
      	adds NIPQUAD_FMT to kernel.h
      	fixes net/netfilter/nf_conntrack_ftp.c
      	changes a few uses of "%u.%u.%u.%u" to NIPQUAD_FMT for symmetry to NIP6_FMT
      Signed-off-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      46b86a2d
  25. 08 1月, 2006 1 次提交
  26. 30 8月, 2005 1 次提交
  27. 21 6月, 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