From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <netdev@vger.kernel.org>, David George <David.George@sophos.com>,
"Markus Trapp" <markus.trapp@secunet.com>
Subject: Re: [PATCH] xfrm: Use xfrm_state selector for BEET input
Date: Wed, 7 Jun 2023 10:47:45 +0200 [thread overview]
Message-ID: <ZIBEMe8SXYMIuOqK@gauss3.secunet.de> (raw)
In-Reply-To: <ZIBCFyszqwJlZd/V@gondor.apana.org.au>
On Wed, Jun 07, 2023 at 04:38:47PM +0800, Herbert Xu wrote:
> On Tue, Jun 06, 2023 at 12:45:29PM +0200, Steffen Klassert wrote:
> >
> > the assumption that the L4 protocol on BEET mode can be
> > just IPIP or BEETPH seems not to be correct. One of
> > our testcaces hit the second WARN_ON_ONCE() in
> > xfrm_prepare_input. In that case the L4 protocol
> > is UDP. Looks like we need some other way to
> > dertermine the inner protocol family.
>
> Oops, that was a thinko on my part:
>
> ---8<---
> For BEET the inner address and therefore family is stored in the
> xfrm_state selector. Use that when decapsulating an input packet
> instead of incorrectly relying on a non-existent tunnel protocol.
>
> Fixes: 5f24f41e8ea6 ("xfrm: Remove inner/outer modes from input path")
> Reported-by: Steffen Klassert <steffen.klassert@secunet.com>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> diff --git a/net/xfrm/xfrm_input.c b/net/xfrm/xfrm_input.c
> index 39fb91ff23d9..bdaed1d1ff97 100644
> --- a/net/xfrm/xfrm_input.c
> +++ b/net/xfrm/xfrm_input.c
> @@ -330,11 +330,10 @@ xfrm_inner_mode_encap_remove(struct xfrm_state *x,
> {
> switch (x->props.mode) {
> case XFRM_MODE_BEET:
> - switch (XFRM_MODE_SKB_CB(skb)->protocol) {
> - case IPPROTO_IPIP:
> - case IPPROTO_BEETPH:
> + switch (x->sel.family) {
Hm, I thought about that one too. But x->sel.family can
also be AF_UNSPEC, in which case we used the address
family of the inner mode before your change.
> + case AF_INET:
> return xfrm4_remove_beet_encap(x, skb);
> - case IPPROTO_IPV6:
> + case AF_INET6:
> return xfrm6_remove_beet_encap(x, skb);
> }
> break;
> --
> Email: Herbert Xu <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2023-06-07 8:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 9:26 [PATCH] xfrm: Remove inner/outer modes from input path Herbert Xu
2023-03-15 11:05 ` Steffen Klassert
2023-06-06 10:45 ` Steffen Klassert
2023-06-07 8:38 ` [PATCH] xfrm: Use xfrm_state selector for BEET input Herbert Xu
2023-06-07 8:47 ` Steffen Klassert [this message]
2023-06-07 8:50 ` Herbert Xu
2023-06-07 8:57 ` Steffen Klassert
2023-06-07 9:04 ` Herbert Xu
2023-06-12 11:46 ` Steffen Klassert
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=ZIBEMe8SXYMIuOqK@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=David.George@sophos.com \
--cc=herbert@gondor.apana.org.au \
--cc=markus.trapp@secunet.com \
--cc=netdev@vger.kernel.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).