From: Simon Horman <horms@kernel.org>
To: Chiachang Wang <chiachangwang@google.com>
Cc: netdev@vger.kernel.org, steffen.klassert@secunet.com,
leonro@nvidia.com, yumike@google.com, stanleyjhu@google.com
Subject: Re: [PATCH ipsec v1 2/2] xfrm: Migrate offload configuration
Date: Wed, 22 Jan 2025 13:05:15 +0000 [thread overview]
Message-ID: <20250122130515.GE390877@kernel.org> (raw)
In-Reply-To: <20250122120941.2634198-3-chiachangwang@google.com>
On Wed, Jan 22, 2025 at 12:09:41PM +0000, Chiachang Wang wrote:
> If the SA contains offload configuration, the migration
> path should update the SA as well.
>
> This change supports SA migration with the offload attribute
> configured. This allows the device to migrate with offload
> configuration.
>
> Test: Endable both in/out IPSec crypto offload, and verify
> with Android device on both WiFi/cellular network,
> including:
> 1. WiFi + offload -> Cellular + offload
> 2. WiFi + offload -> Cellular + no offload
> 3. WiFi + no offload -> Cellular + offload
> 4. Wifi + no offload -> Cellular + no offload
> 5. Cellular + offload -> WiFi + offload
> 6. Cellular + no offload -> WiFi + offload
> 7. Cellular + offload -> WiFi + no offload
> 8. Cell + no offload -> WiFi + no offload
> Signed-off-by: Chiachang Wang <chiachangwang@google.com>
...
> diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
> index 46d75980eb2e..2fdb4ea97844 100644
> --- a/net/xfrm/xfrm_state.c
> +++ b/net/xfrm/xfrm_state.c
> @@ -2007,22 +2007,30 @@ EXPORT_SYMBOL(xfrm_migrate_state_find);
>
> struct xfrm_state *xfrm_state_migrate(struct xfrm_state *x,
> struct xfrm_migrate *m,
> - struct xfrm_encap_tmpl *encap)
> + struct xfrm_encap_tmpl *encap,
> + struct net *net,
> + struct xfrm_user_offload *xuo,
> + struct netlink_ext_ack *extack)
> {
> struct xfrm_state *xc;
> -
> + bool offload = (xuo);
> xc = xfrm_state_clone(x, encap);
> if (!xc)
> return NULL;
>
> xc->props.family = m->new_family;
>
> - if (xfrm_init_state(xc) < 0)
> + if (__xfrm_init_state(xc, true, offload, NULL) < 0)
> goto error;
>
> + x->km.state = XFRM_STATE_VALID;
> memcpy(&xc->id.daddr, &m->new_daddr, sizeof(xc->id.daddr));
> memcpy(&xc->props.saddr, &m->new_saddr, sizeof(xc->props.saddr));
>
> + /* configure the hardware if offload is requested */
> + if (offload & xfrm_dev_state_add(net, xc, xuo, extack))
Hi Chiachang Wang,
This looks like it is intended to be a logical and (&&)
rather than a bitwise and (&).
Flagged by Smatch.
> + goto error;
> +
> /* add state */
> if (xfrm_addr_equal(&x->id.daddr, &m->new_daddr, m->new_family)) {
> /* a care is needed when the destination address of the
prev parent reply other threads:[~2025-01-22 13:05 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 ` [PATCH ipsec v1 1/2] xfrm: Update offload configuration during SA updates Chiachang Wang
2025-01-22 13:07 ` 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 [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=20250122130515.GE390877@kernel.org \
--to=horms@kernel.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.