From: Hangbin Liu <liuhangbin@gmail.com>
To: Erwan Dufour <mrarmonius@gmail.com>
Cc: netdev@vger.kernel.org, steffen.klassert@secunet.com,
herbert@gondor.apana.org.au, davem@davemloft.net,
jv@jvosburgh.net, saeedm@nvidia.com, tariqt@nvidia.com,
erwan.dufour@withings.com, cratiu@nvidia.com, leon@kernel.org
Subject: Re: [PATCH net-next v2] xfrm: bonding: Add XFRM packet-offload for active-backup
Date: Wed, 9 Jul 2025 02:01:34 +0000 [thread overview]
Message-ID: <aG3NfmO5wsQWKaoz@fedora> (raw)
In-Reply-To: <20250706145803.47491-2-mramonius@gmail.com>
Hi Erwan,
On Sun, Jul 06, 2025 at 04:58:04PM +0200, Erwan Dufour wrote:
> From: Erwan Dufour <erwan.dufour@withings.com>
>
> New features added:
> - Use of packet offload added for XFRM in active-backup
> - Behaviour modification when changing primary slave to prevent reuse of IV.
...
>
> -static void bond_ipsec_add_sa_all(struct bonding *bond)
> +static void bond_ipsec_add_sa_sp_all(struct bonding *bond)
> {
> struct net_device *bond_dev = bond->dev;
> struct net_device *real_dev;
> struct bond_ipsec *ipsec;
> struct slave *slave;
> + int err;
>
> slave = rtnl_dereference(bond->curr_active_slave);
> real_dev = slave ? slave->dev : NULL;
> if (!real_dev)
> return;
>
> - mutex_lock(&bond->ipsec_lock);
> + mutex_lock(&bond->ipsec_lock_sa);
> if (!real_dev->xfrmdev_ops ||
> !real_dev->xfrmdev_ops->xdo_dev_state_add ||
> netif_is_bond_master(real_dev)) {
> - if (!list_empty(&bond->ipsec_list))
> + if (!list_empty(&bond->ipsec_list_sa))
> slave_warn(bond_dev, real_dev,
> "%s: no slave xdo_dev_state_add\n",
> __func__);
> - goto out;
> + goto out_sa;
> }
>
> - list_for_each_entry(ipsec, &bond->ipsec_list, list) {
> - /* If new state is added before ipsec_lock acquired */
> + list_for_each_entry(ipsec, &bond->ipsec_list_sa, list) {
> + /* If new state is added before ipsec_lock_sa acquired */
> if (ipsec->xs->xso.real_dev == real_dev)
> continue;
>
> - if (real_dev->xfrmdev_ops->xdo_dev_state_add(real_dev,
> - ipsec->xs, NULL)) {
> - slave_warn(bond_dev, real_dev, "%s: failed to add SA\n", __func__);
> + err = __xfrm_state_delete(ipsec->xs);
> + if (!err)
> + km_state_expired(ipsec->xs, 1, 0);
> +
> + xfrm_audit_state_delete(ipsec->xs, err ? 0 : 1, true);
I see you delete ipsec->xs here. Do you mean to prevent reuse of IV?
But I can't find you add the xs back to new slave.
> + }
> +out_sa:
> + mutex_unlock(&bond->ipsec_lock_sa);
> +
> + mutex_lock(&bond->ipsec_lock_sp);
> + if (!real_dev->xfrmdev_ops ||
> + !real_dev->xfrmdev_ops->xdo_dev_policy_add ||
> + netif_is_bond_master(real_dev)) {
> + if (!list_empty(&bond->ipsec_list_sp))
> + slave_warn(bond_dev, real_dev,
> + "%s: no slave xdo_dev_policy_add\n",
> + __func__);
> + goto out_sp;
> + }
> + list_for_each_entry(ipsec, &bond->ipsec_list_sp, list) {
> + if (ipsec->xp->xdo.real_dev == real_dev)
> + continue;
> +
> + if (real_dev->xfrmdev_ops->xdo_dev_policy_add(real_dev,
> + ipsec->xp,
> + NULL)) {
> + slave_warn(bond_dev, real_dev,
> + "%s: failed to add SP\n", __func__);
> continue;
Here you do xdo_dev_policy_add(). What about the xdo_dev_state_add()?
> }
>
> - spin_lock_bh(&ipsec->xs->lock);
> - /* xs might have been killed by the user during the migration
> - * to the new dev, but bond_ipsec_del_sa() should have done
> - * nothing, as xso.real_dev is NULL.
> - * Delete it from the device we just added it to. The pending
> - * bond_ipsec_free_sa() call will do the rest of the cleanup.
> - */
> - if (ipsec->xs->km.state == XFRM_STATE_DEAD &&
> - real_dev->xfrmdev_ops->xdo_dev_state_delete)
> - real_dev->xfrmdev_ops->xdo_dev_state_delete(real_dev,
> - ipsec->xs);
Here the xdo_dev_state_delete() is called when km.state == XFRM_STATE_DEAD.
Why we remove this?
> - ipsec->xs->xso.real_dev = real_dev;
> - spin_unlock_bh(&ipsec->xs->lock);
> + write_lock_bh(&ipsec->xp->lock);
> + ipsec->xp->xdo.real_dev = real_dev;
> + write_unlock_bh(&ipsec->xp->lock);
> }
> -out:
> - mutex_unlock(&bond->ipsec_lock);
> +
> +out_sp:
> + mutex_unlock(&bond->ipsec_lock_sp);
> }
Thanks
Hangbin
next prev parent reply other threads:[~2025-07-09 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-06 14:58 [PATCH net-next v2] xfrm: bonding: Add XFRM packet-offload for active-backup Erwan Dufour
2025-07-09 2:01 ` Hangbin Liu [this message]
2025-07-09 21:57 ` Erwan Dufour
2025-07-15 18:23 ` Erwan Dufour
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=aG3NfmO5wsQWKaoz@fedora \
--to=liuhangbin@gmail.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=erwan.dufour@withings.com \
--cc=herbert@gondor.apana.org.au \
--cc=jv@jvosburgh.net \
--cc=leon@kernel.org \
--cc=mrarmonius@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=steffen.klassert@secunet.com \
--cc=tariqt@nvidia.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