From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, jv@jvosburgh.net, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
petrm@nvidia.com, linux-kselftest@vger.kernel.org
Subject: Re: [PATCHv3 net 1/2] bonding: fix xfrm offload feature setup on active-backup mode
Date: Tue, 30 Sep 2025 08:20:07 +0000 [thread overview]
Message-ID: <175922040752.1888939.8527020251464882596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250925023304.472186-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 25 Sep 2025 02:33:03 +0000 you wrote:
> The active-backup bonding mode supports XFRM ESP offload. However, when
> a bond is added using command like `ip link add bond0 type bond mode 1
> miimon 100`, the `ethtool -k` command shows that the XFRM ESP offload is
> disabled. This occurs because, in bond_newlink(), we change bond link
> first and register bond device later. So the XFRM feature update in
> bond_option_mode_set() is not called as the bond device is not yet
> registered, leading to the offload feature not being set successfully.
>
> [...]
Here is the summary with links:
- [PATCHv3,net,1/2] bonding: fix xfrm offload feature setup on active-backup mode
https://git.kernel.org/netdev/net/c/5b66169f6be4
- [PATCHv3,net,2/2] selftests: bonding: add ipsec offload test
https://git.kernel.org/netdev/net/c/99e4c35eada9
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:[~2025-09-30 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 2:33 [PATCHv3 net 1/2] bonding: fix xfrm offload feature setup on active-backup mode Hangbin Liu
2025-09-25 2:33 ` [PATCHv3 net 2/2] selftests: bonding: add ipsec offload test Hangbin Liu
2025-10-01 8:37 ` [PATCHv3 net 2/2] selftests: bonding: add ipsec offload test: manual merge Matthieu Baerts
2025-10-02 1:20 ` Hangbin Liu
2025-09-30 8:20 ` 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=175922040752.1888939.8527020251464882596.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=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
/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