From: Chiachang Wang <chiachangwang@google.com>
To: netdev@vger.kernel.org, steffen.klassert@secunet.com, leonro@nvidia.com
Cc: yumike@google.com, stanleyjhu@google.com, chiachangwang@google.com
Subject: [PATCH ipsec v1 1/2] xfrm: Update offload configuration during SA updates
Date: Wed, 22 Jan 2025 12:09:40 +0000 [thread overview]
Message-ID: <20250122120941.2634198-2-chiachangwang@google.com> (raw)
In-Reply-To: <20250122120941.2634198-1-chiachangwang@google.com>
The offload setting is set to HW when the ipsec session is
initialized but cannot be changed until the session is torn
down. The session administrator should be able to update
the SA via netlink message.
This patch ensures that when a SA is updated, the associated
offload configuration is also updated. This is necessary to
maintain consistency between the SA and the offload device,
especially when the device is configured for IPSec offload.
Any offload changes to the SA are reflected in the kernel
and offload device.
Test: Enable both in/out crypto offload, and verify with
Android device on WiFi/cellular network, including
1. WiFi + crypto offload -> WiFi + no offload
2. WiFi + no offload -> WiFi + crypto offload
3. Cellular + crypto offload -> Cellular + no offload
4. Cellular + no offload -> Cellular + crypto offload
Signed-off-by: Chiachang Wang <chiachangwang@google.com>
---
net/xfrm/xfrm_state.c | 24 +++++++++++++++++++++++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
index 67ca7ac955a3..46d75980eb2e 100644
--- a/net/xfrm/xfrm_state.c
+++ b/net/xfrm/xfrm_state.c
@@ -2047,7 +2047,8 @@ int xfrm_state_update(struct xfrm_state *x)
int err;
int use_spi = xfrm_id_proto_match(x->id.proto, IPSEC_PROTO_ANY);
struct net *net = xs_net(x);
-
+ struct xfrm_dev_offload *xso;
+ struct net_device *old_dev;
to_put = NULL;
spin_lock_bh(&net->xfrm.xfrm_state_lock);
@@ -2124,7 +2125,28 @@ int xfrm_state_update(struct xfrm_state *x)
__xfrm_state_bump_genids(x1);
spin_unlock_bh(&net->xfrm.xfrm_state_lock);
}
+#ifdef CONFIG_XFRM_OFFLOAD
+ x1->type_offload = x->type_offload;
+
+ if (memcmp(&x1->xso, &x->xso, sizeof(x1->xso))) {
+ old_dev = x1->xso.dev;
+ memcpy(&x1->xso, &x->xso, sizeof(x1->xso));
+
+ if (old_dev)
+ old_dev->xfrmdev_ops->xdo_dev_state_delete(x1);
+
+ if (x1->xso.dev) {
+ xso = &x1->xso;
+ netdev_hold(xso->dev, &xso->dev_tracker, GFP_ATOMIC);
+ err = xso->dev->xfrmdev_ops->xdo_dev_state_add(x1, NULL);
+ if (err) {
+ netdev_put(xso->dev, &xso->dev_tracker);
+ goto fail;
+ }
+ }
+ }
+#endif
err = 0;
x->km.state = XFRM_STATE_DEAD;
__xfrm_state_put(x);
--
2.48.1.262.g85cc9f2d1e-goog
next prev parent reply other threads:[~2025-01-22 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 12:09 [PATCH ipsec v1 0/2] Update offload configuration with SA Chiachang Wang
2025-01-22 12:09 ` Chiachang Wang [this message]
2025-01-22 13:07 ` [PATCH ipsec v1 1/2] xfrm: Update offload configuration during SA updates Leon Romanovsky
2025-01-22 13:08 ` Simon Horman
2025-02-20 7:35 ` [PATCH ipsec v2 0/1] Update offload configuration with SA Chiachang Wang
2025-02-20 7:35 ` [PATCH ipsec v2 1/1] xfrm: Migrate offload configuration Chiachang Wang
2025-02-21 11:02 ` kernel test robot
2025-02-23 11:21 ` Leon Romanovsky
2025-01-22 12:09 ` [PATCH ipsec v1 2/2] " Chiachang Wang
2025-01-22 13:05 ` Simon Horman
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=20250122120941.2634198-2-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).