From: Hangbin Liu <liuhangbin@gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Sabrina Dubroca <sd@queasysnail.net>,
netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Tariq Toukan <tariqt@nvidia.com>, Jianbo Liu <jianbol@nvidia.com>,
Simon Horman <horms@kernel.org>
Subject: Re: [PATCHv3 net-next 2/3] bonding: Add ESN support to IPSec HW offload
Date: Fri, 23 Aug 2024 20:48:21 +0800 [thread overview]
Message-ID: <ZsiFFX7AizhF-ptV@Laptop-X1> (raw)
In-Reply-To: <ZshHTlUb/BCtvCT0@gauss3.secunet.de>
Hi Steffen,
On Fri, Aug 23, 2024 at 10:24:46AM +0200, Steffen Klassert wrote:
> > Thanks for your comments. I'm not familiar with IPsec state.
> > Do you mean something like
> >
> > diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
> > index f74bacf071fc..8a51d0812564 100644
> > --- a/drivers/net/bonding/bond_main.c
> > +++ b/drivers/net/bonding/bond_main.c
> > @@ -477,6 +477,7 @@ static void bond_ipsec_add_sa_all(struct bonding *bond)
> > struct net_device *bond_dev = bond->dev;
> > struct bond_ipsec *ipsec;
> > struct slave *slave;
> > + struct km_event c;
> >
> > rcu_read_lock();
> > slave = rcu_dereference(bond->curr_active_slave);
> > @@ -498,6 +499,13 @@ static void bond_ipsec_add_sa_all(struct bonding *bond)
> > spin_lock_bh(&bond->ipsec_lock);
> > list_for_each_entry(ipsec, &bond->ipsec_list, list) {
> > ipsec->xs->xso.real_dev = slave->dev;
> > +
> > + ipsec->xs->km.state = XFRM_STATE_VALID;
> > + c.data.hard = 1;
> > + c.portid = 0;
> > + c.event = XFRM_MSG_NEWSA;
> > + km_state_notify(x, &c);
>
> The xfrm stack does that already when inserting the state.
Thanks for this info.
>
> > +
> > if (slave->dev->xfrmdev_ops->xdo_dev_state_add(ipsec->xs, NULL)) {
> > slave_warn(bond_dev, slave->dev, "%s: failed to add SA\n", __func__);
> > ipsec->xs->xso.real_dev = NULL;
> > @@ -580,6 +588,8 @@ static void bond_ipsec_del_sa_all(struct bonding *bond)
> > "%s: no slave xdo_dev_state_delete\n",
> > __func__);
> > } else {
> > + ipsec->xs->km.state = XFRM_STATE_EXPIRED;
>
> I think you also need to set 'x->km.dying = 1'.
>
> > + km_state_expired(ipsec->xs, 1, 0);
>
> Please test this at least with libreswan and strongswan. The state is
> actually not expired, so not sure if the IKE daemons behave as we want
> in that case.
OK, this fix should be not related the current patch set. I will post this fix
after more tests.
Thanks
Hangbin
>
> Downside of this approach is that you loose some packets until the new
> SA is negotiated, as Sabrina mentioned.
next prev parent reply other threads:[~2024-08-23 12:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 0:48 [PATCHv3 net-next 0/3] Bonding: support new xfrm state offload functions Hangbin Liu
2024-08-20 0:48 ` [PATCHv3 net-next 1/3] bonding: add common function to check ipsec device Hangbin Liu
2024-08-20 12:51 ` Nikolay Aleksandrov
2024-08-20 0:48 ` [PATCHv3 net-next 2/3] bonding: Add ESN support to IPSec HW offload Hangbin Liu
2024-08-20 15:33 ` Sabrina Dubroca
2024-08-21 2:32 ` Hangbin Liu
2024-08-21 12:30 ` Steffen Klassert
2024-08-21 13:26 ` Hangbin Liu
2024-08-21 13:39 ` Sabrina Dubroca
2024-08-21 14:03 ` Steffen Klassert
2024-08-21 17:20 ` Sabrina Dubroca
2024-08-22 7:12 ` Steffen Klassert
2024-08-22 0:33 ` Hangbin Liu
2024-08-22 7:10 ` Steffen Klassert
2024-08-22 8:33 ` Hangbin Liu
2024-08-23 8:24 ` Steffen Klassert
2024-08-23 12:48 ` Hangbin Liu [this message]
2024-08-22 8:39 ` Sabrina Dubroca
2024-08-22 9:55 ` Steffen Klassert
2024-08-20 0:48 ` [PATCHv3 net-next 3/3] bonding: support xfrm state update Hangbin Liu
2024-08-20 14:38 ` Sabrina Dubroca
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=ZsiFFX7AizhF-ptV@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=j.vosburgh@gmail.com \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=sd@queasysnail.net \
--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;
as well as URLs for NNTP newsgroup(s).