From: Florian Westphal <fw@strlen.de>
To: netdev@vger.kernel.org
Cc: steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
Florian Westphal <fw@strlen.de>
Subject: [PATCH ipsec-next 0/5] xfrm: ipv6: remove hdr_off indirection
Date: Thu, 10 Jun 2021 14:06:24 +0200 [thread overview]
Message-ID: <20210610120629.23088-1-fw@strlen.de> (raw)
IPV6 xfrm moves mutable extension headers to make space for the
encapsulation header.
For Mobile ipv6 sake this uses an indirect call (ipv6 can be built
as module).
These patches remove those indirections by placing a
small parsing function in the xfrm core.
While at it, the merged dstopt/rt hdroff function is
realigned with ip6_find_1stfragopt (where they were copied from).
ip6_find_1stfragopt received bug fixes that were missing from the
cloned ones.
Florian Westphal (5):
xfrm: ipv6: add xfrm6_hdr_offset helper
xfrm: ipv6: move mip6_destopt_offset into xfrm core
xfrm: ipv6: move mip6_rthdr_offset into xfrm core
xfrm: remove hdr_offset indirection
xfrm: merge dstopt and routing hdroff functions
include/net/xfrm.h | 3 --
net/ipv6/ah6.c | 1 -
net/ipv6/esp6.c | 1 -
net/ipv6/ipcomp6.c | 1 -
net/ipv6/mip6.c | 97 -----------------------------------------
net/ipv6/xfrm6_output.c | 7 ---
net/xfrm/xfrm_output.c | 78 ++++++++++++++++++++++++++++++++-
7 files changed, 76 insertions(+), 112 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-10 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 12:06 Florian Westphal [this message]
2021-06-10 12:06 ` [PATCH ipsec-next 1/5] xfrm: ipv6: add xfrm6_hdr_offset helper Florian Westphal
2021-06-10 12:06 ` [PATCH ipsec-next 2/5] xfrm: ipv6: move mip6_destopt_offset into xfrm core Florian Westphal
2021-06-10 12:06 ` [PATCH ipsec-next 3/5] xfrm: ipv6: move mip6_rthdr_offset " Florian Westphal
2021-06-10 12:06 ` [PATCH ipsec-next 4/5] xfrm: remove hdr_offset indirection Florian Westphal
2021-06-10 12:06 ` [PATCH ipsec-next 5/5] xfrm: merge dstopt and routing hdroff functions Florian Westphal
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=20210610120629.23088-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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).