From: Antony Antony <antony.antony@secunet.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
David Ahern <dsahern@gmail.com>
Cc: <netdev@vger.kernel.org>, <devel@linux-ipsec.org>,
Steffen Klassert <steffen.klassert@secunet.com>,
Eyal Birger <eyal.birger@gmail.com>,
"Nicolas Dichtel" <nicolas.dichtel@6wind.com>,
Sabrina Dubroca <sd@queasysnail.net>,
Christian Hopps <chopps@chopps.org>,
Antony Antony <antony.antony@secunet.com>
Subject: [PATCH RFC iproute2-next 0/3] xfrm: Add support for SA direction and output cleanup
Date: Sun, 19 May 2024 20:36:14 +0200 [thread overview]
Message-ID: <cover.1716143499.git.antony.antony@secunet.com> (raw)
Kernel added SA direction in commit
179a6f5df8da ("Merge tag 'ipsec-next-2024-05-03' of git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next")
This commit adds iproute2 support for SA direction.
Additionally, redundant fields in the "ip xfrm state" output are
removed when SA direction is set. This series keeps the old behavior
when the direction is not set.
Signed-off-by: Antony Antony <antony.antony@secunet.com>
---
Antony Antony (3):
uapi: Update kernel headers xfrm.h
xfrm: support xfrm SA direction attribute
xfrm: update ip xfrm state output for SA with direction attribute
include/uapi/linux/xfrm.h | 6 ++
ip/ipxfrm.c | 126 +++++++++++++++++++++++++++-----------
ip/xfrm_state.c | 44 +++++++++++--
3 files changed, 136 insertions(+), 40 deletions(-)
--
2.30.2
next reply other threads:[~2024-05-19 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 18:36 Antony Antony [this message]
2024-05-19 18:37 ` [PATCH RFC iproute2-next 1/3] uapi: Update kernel headers xfrm.h Antony Antony
2024-05-19 18:37 ` [PATCH RFC iproute2-next 2/3] xfrm: support xfrm SA direction attribute Antony Antony
2024-05-19 22:58 ` Stephen Hemminger
2024-05-22 9:26 ` Christian Hopps
2024-05-23 14:56 ` David Ahern
2024-05-19 18:37 ` [PATCH RFC iproute2-next 3/3] xfrm: update ip xfrm state output for SA with " Antony Antony
2024-05-19 22:59 ` Stephen Hemminger
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=cover.1716143499.git.antony.antony@secunet.com \
--to=antony.antony@secunet.com \
--cc=chopps@chopps.org \
--cc=devel@linux-ipsec.org \
--cc=dsahern@gmail.com \
--cc=eyal.birger@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=sd@queasysnail.net \
--cc=steffen.klassert@secunet.com \
--cc=stephen@networkplumber.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).