Skip to content

L
linux-davinci
An error occurred fetching the project authors.
Switch branch/tag
  1. 10 Oct, 2007 1 commit
  3. 11 Jul, 2007 1 commit
  5. 17 May, 2007 2 commits
  7. 09 May, 2007 1 commit
  9. 26 Apr, 2007 2 commits
  11. 26 Feb, 2007 1 commit
  13. 17 Feb, 2007 1 commit
  15. 03 Dec, 2006 3 commits
  17. 04 Oct, 2006 1 commit
  19. 03 Oct, 2006 2 commits
  21. 25 Sep, 2006 2 commits
  23. 22 Sep, 2006 1 commit
  25. 21 Sep, 2006 1 commit
  27. 10 Jul, 2006 1 commit
  29. 18 Jun, 2006 4 commits
  31. 29 Mar, 2006 1 commit
    • Herbert Xu's avatar
      [INET]: Introduce tunnel4/tunnel6 · d2acc347
      Herbert Xu authored 
      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: default avatarHerbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      d2acc347
  33. 03 Jan, 2006 1 commit
  35. 29 Aug, 2005 6 commits
  37. 27 Jul, 2005 1 commit
  39. 19 Jul, 2005 2 commits
  41. 18 Jul, 2005 1 commit
  43. 12 Jul, 2005 1 commit
    • Sam Ravnborg's avatar
      [NET]: move config options out to individual protocols · 6a2e9b73
      Sam Ravnborg authored 
      Move the protocol specific config options out to the specific protocols.
With this change net/Kconfig now starts to become readable and serve as a
good basis for further re-structuring.

The menu structure is left almost intact, except that indention is
fixed in most cases. Most visible are the INET changes where several
"depends on INET" are replaced with a single ifdef INET / endif pair.

Several new files were created to accomplish this change - they are
small but serve the purpose that config options are now distributed
out where they belongs.
Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      6a2e9b73
  45. 26 Jun, 2005 2 commits
  47. 25 Jun, 2005 1 commit