From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: yoshfuji@linux-ipv6.org, kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH 2/11] [IPSEC]: Move tunnel parsing for IPv4 out of xfrm4_input
Date: Wed, 17 Oct 2007 21:29:02 -0700 (PDT) [thread overview]
Message-ID: <20071017.212902.68160683.davem@davemloft.net> (raw)
In-Reply-To: <E1Ii9yL-0006Gp-00@gondolin.me.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Wed, 17 Oct 2007 22:34:09 +0800
> [IPSEC]: Move tunnel parsing for IPv4 out of xfrm4_input
>
> This patch moves the tunnel parsing for IPv4 out of xfrm4_input and into
> xfrm4_tunnel. This change is in line with what IPv6 does and will allow
> us to merge the two input functions.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Applied.
next prev parent reply other threads:[~2007-10-18 4:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 14:29 [0/11] Various xfrm fixes and clean-ups Herbert Xu
2007-10-17 14:34 ` [PATCH 1/11] [IPSEC]: Fix pure tunnel modes involving IPv6 Herbert Xu
2007-10-18 4:28 ` David Miller
2007-10-17 14:34 ` [PATCH 2/11] [IPSEC]: Move tunnel parsing for IPv4 out of xfrm4_input Herbert Xu
2007-10-18 4:29 ` David Miller [this message]
2007-10-17 14:34 ` [PATCH 3/11] [IPSEC]: Get nexthdr from caller in xfrm6_rcv_spi Herbert Xu
2007-10-18 4:29 ` David Miller
2007-10-17 14:34 ` [PATCH 4/11] [IPSEC]: Move ip_summed zapping out of xfrm6_rcv_spi Herbert Xu
2007-10-18 4:30 ` David Miller
2007-10-17 14:34 ` [PATCH 5/11] [IPSEC]: Fix length check in xfrm_parse_spi Herbert Xu
2007-10-18 4:30 ` David Miller
2007-10-17 14:34 ` [PATCH 6/11] [IPSEC]: Move type and mode map into xfrm_state.c Herbert Xu
2007-10-18 4:31 ` David Miller
2007-10-17 14:34 ` [PATCH 7/11] [IPSEC]: Add missing BEET checks Herbert Xu
2007-10-18 4:31 ` David Miller
2007-10-17 14:34 ` [PATCH 8/11] [IPSEC]: Store afinfo pointer in xfrm_mode Herbert Xu
2007-10-18 4:34 ` David Miller
2007-10-17 14:34 ` [PATCH 9/11] [IPSEC]: Use the top IPv4 route's peer instead of the bottom Herbert Xu
2007-10-18 4:34 ` David Miller
2007-10-17 14:34 ` [PATCH 10/11] [IPSEC]: Disallow combinations of RO and AH/ESP/IPCOMP Herbert Xu
2007-10-18 4:35 ` David Miller
2007-10-22 6:09 ` [PATCH] [IPSEC] IPV6: Fix to add tunnel mode SA correctly Masahide NAKAMURA
2007-10-22 8:37 ` Herbert Xu
2007-10-22 9:42 ` David Miller
2007-10-22 6:11 ` [RFC][PATCH 0/3][XFRM]: Support packet processing error statistics Masahide NAKAMURA
2007-10-22 8:50 ` Herbert Xu
2007-10-22 8:42 ` Masahide NAKAMURA
2007-10-22 12:28 ` jamal
2007-10-23 7:08 ` Masahide NAKAMURA
2007-10-23 19:47 ` jamal
2007-10-24 3:30 ` Masahide NAKAMURA
2007-10-24 12:18 ` jamal
2007-10-25 9:06 ` Masahide NAKAMURA
2007-10-24 3:59 ` YOSHIFUJI Hideaki / 吉藤英明
2007-10-24 12:25 ` jamal
2007-10-22 6:11 ` [RFC][PATCH 1/3][XFRM]: Define packet processing statistics Masahide NAKAMURA
2007-10-22 6:11 ` [RFC][PATCH 2/3][XFRM]: Support to increment " Masahide NAKAMURA
2007-10-22 6:11 ` [RFC][PATCH 3/3][XFRM]: Add packet processing statistics option Masahide NAKAMURA
2007-10-17 14:34 ` [PATCH 11/11] [IPSEC]: Rename mode to outer_mode and add inner_mode Herbert Xu
2007-10-17 15:26 ` Herbert Xu
2007-10-18 4:36 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071017.212902.68160683.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).