From: Chiachang Wang <chiachangwang@google.com>
To: netdev@vger.kernel.org, steffen.klassert@secunet.com, leonro@nvidia.com
Cc: chiachangwang@google.com, stanleyjhu@google.com, yumike@google.com
Subject: [PATCH ipsec-next v4 0/2] Update offload configuration with SA
Date: Mon, 10 Mar 2025 09:16:18 +0000 [thread overview]
Message-ID: <20250310091620.2706700-1-chiachangwang@google.com> (raw)
The current Security Association (SA) offload setting
cannot be modified without removing and re-adding the
SA with the new configuration. Although existing netlink
messages allow SA migration, the offload setting will
be removed after migration.
This patchset enhances SA migration to include updating
the offload setting. This is beneficial for devices that
support IPsec session management.
Chiachang Wang (2):
xfrm: Migrate offload configuration
xfrm: Refactor migration setup during the cloning process
include/net/xfrm.h | 8 ++++++--
net/key/af_key.c | 2 +-
net/xfrm/xfrm_policy.c | 4 ++--
net/xfrm/xfrm_state.c | 25 +++++++++++++++++--------
net/xfrm/xfrm_user.c | 15 ++++++++++++---
5 files changed, 38 insertions(+), 16 deletions(-)
---
v3 -> v4:
- Change the target tree to ipsec-next
- Rebase commit to adopt updated xfrm_init_state()
- Remove redundant variable to rely on validiaty of pointer
- Refactor xfrm_migrate copy into xfrm_state_clone and rename the
method
v2 -> v3:
- Update af_key.c to address kbuild error
v1 -> v2:
- Revert "xfrm: Update offload configuration during SA update"
change as the patch can be protentially handled in the
hardware without the change.
- Address review feedback to correct the logic in the
xfrm_state_migrate in the migration offload configuration
change.
- Revise the commit message for "xfrm: Migrate offload configuration"
--
2.49.0.rc0.332.g42c0ae87b1-goog
next reply other threads:[~2025-03-10 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 9:16 Chiachang Wang [this message]
2025-03-10 9:16 ` [PATCH ipsec-next v4 1/2] xfrm: Migrate offload configuration Chiachang Wang
2025-03-10 11:54 ` Leon Romanovsky
2025-03-10 9:16 ` [PATCH ipsec-next v4 2/2] xfrm: Refactor migration setup during the cloning process Chiachang Wang
2025-03-10 11:52 ` Leon Romanovsky
2025-03-10 12:20 ` Chiachang Wang
2025-03-12 13:00 ` Leon Romanovsky
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=20250310091620.2706700-1-chiachangwang@google.com \
--to=chiachangwang@google.com \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=stanleyjhu@google.com \
--cc=steffen.klassert@secunet.com \
--cc=yumike@google.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).