From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH] xfrm: Remove inner/outer modes from output path
Date: Wed, 15 Mar 2023 12:06:28 +0100 [thread overview]
Message-ID: <ZBGmtKFTYbQJSgEy@gauss3.secunet.de> (raw)
In-Reply-To: <ZAr7EHeGkqVUr+z5@gondor.apana.org.au>
On Fri, Mar 10, 2023 at 05:40:32PM +0800, Herbert Xu wrote:
> The inner/outer modes were added to abstract out common code that
> were once duplicated between IPv4 and IPv6. As time went on the
> abstractions have been removed and we are now left with empty
> shells that only contain duplicate information. These can be
> removed one-by-one as the same information is already present
> elsewhere in the xfrm_state object.
>
> Just like the input-side, removing this from the output code
> makes it possible to use transport-mode SAs underneath an
> inter-family tunnel mode SA.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Also applied to ipsec-next, thanks a lot!
prev parent reply other threads:[~2023-03-15 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 9:40 [PATCH] xfrm: Remove inner/outer modes from output path Herbert Xu
2023-03-15 11:06 ` Steffen Klassert [this message]
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=ZBGmtKFTYbQJSgEy@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=herbert@gondor.apana.org.au \
--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).