From: patchwork-bot+netdevbpf@kernel.org
To: David Dai <zdai@linux.ibm.com>
Cc: jv@jvosburgh.net, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
jarod@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, hangbin.liu@linux.dev,
pradeeps@linux.ibm.com
Subject: Re: [PATCH net v2 1/1] bonding: crypto offload enabled, non-offload slave failover, rekey failed
Date: Thu, 24 Sep 2026 10:00:05 +0000 [thread overview]
Message-ID: <179024400545.1442619.2930959931801538685.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260918211155.1664493-1-zdai@linux.ibm.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 18 Sep 2026 16:11:55 -0500 you wrote:
> Create a bonding device (i.e. bond0) in active-backup mode, 2 slaves.
> Active slave: offload capable interface (i.e. eth1), primary interface.
> Backup slave: non-offload capable interface(i.e. eth2).
> Configure strongswan service swantl.conf child SA "hw_offload = crypto"
> Start strongswan service
> IPSec Crytpo Offload is enabled on top of bond0. i.e.
> ip xfrm state |grep offload
> crypto offload parameters: dev bond0 dir out mode crypto
> crypto offload parameters: dev bond0 dir in mode crypto
>
> [...]
Here is the summary with links:
- [net,v2,1/1] bonding: crypto offload enabled, non-offload slave failover, rekey failed
https://git.kernel.org/netdev/net/c/00efbbd40bd5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-24 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 21:11 David Dai
2026-09-20 0:41 ` Hangbin Liu
2026-09-24 10:00 ` patchwork-bot+netdevbpf [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=179024400545.1442619.2930959931801538685.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hangbin.liu@linux.dev \
--cc=jarod@redhat.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pradeeps@linux.ibm.com \
--cc=zdai@linux.ibm.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
all inboxes | Powered by JetHome®