Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>, netdev@vger.kernel.org
Cc: Jay Vosburgh <jv@jvosburgh.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
	Petr Machata <petrm@nvidia.com>,
	linux-kselftest@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [PATCHv3 net 2/2] selftests: bonding: add ipsec offload test: manual merge
Date: Wed, 1 Oct 2025 10:37:51 +0200	[thread overview]
Message-ID: <f4f61cb1-a2f5-4105-b051-0b16427fb12b@kernel.org> (raw)
In-Reply-To: <20250925023304.472186-2-liuhangbin@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2908 bytes --]

Hello,

On 25/09/2025 04:33, Hangbin Liu wrote:
> This introduces a test for IPSec offload over bonding, utilizing netdevsim
> for the testing process, as veth interfaces do not support IPSec offload.
> The test will ensure that the IPSec offload functionality remains operational
> even after a failover event occurs in the bonding configuration.
> 
> Here is the test result:
> 
> TEST: bond_ipsec_offload (active_slave eth0)                        [ OK ]
> TEST: bond_ipsec_offload (active_slave eth1)                        [ OK ]
> 
> Reviewed-by: Petr Machata <petrm@nvidia.com>
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> ---
> v3: fix shellcheck errors
> v2: rebase to latest net, no code update
> ---
>  .../selftests/drivers/net/bonding/Makefile    |   3 +-
>  .../drivers/net/bonding/bond_ipsec_offload.sh | 156 ++++++++++++++++++
>  .../selftests/drivers/net/bonding/config      |   4 +
>  3 files changed, 162 insertions(+), 1 deletion(-)
>  create mode 100755 tools/testing/selftests/drivers/net/bonding/bond_ipsec_offload.sh
> 
> diff --git a/tools/testing/selftests/drivers/net/bonding/Makefile b/tools/testing/selftests/drivers/net/bonding/Makefile
> index 44b98f17f8ff..c13ef40e7db1 100644
> --- a/tools/testing/selftests/drivers/net/bonding/Makefile
> +++ b/tools/testing/selftests/drivers/net/bonding/Makefile
> @@ -11,7 +11,8 @@ TEST_PROGS := \
>  	bond_options.sh \
>  	bond-eth-type-change.sh \
>  	bond_macvlan_ipvlan.sh \
> -	bond_passive_lacp.sh
> +	bond_passive_lacp.sh \
> +	bond_ipsec_offload.sh

FYI, we got a small conflict when merging 'net' in 'net-next' in the
MPTCP tree due to this patch applied in 'net':

  99e4c35eada9 ("selftests: bonding: add ipsec offload test")

and this one from 'net-next':

  c2377f1763e9 ("selftests: bonding: add test for LACP actor port priority")

----- Generic Message -----
The best is to avoid conflicts between 'net' and 'net-next' trees but if
they cannot be avoided when preparing patches, a note about how to fix
them is much appreciated.

The conflict has been resolved on our side [1] and the resolution we
suggest is attached to this email. Please report any issues linked to
this conflict resolution as it might be used by others. If you worked on
the mentioned patches, don't hesitate to ACK this conflict resolution.
---------------------------

Regarding this conflict, I simply added the new files from both trees:

  bond_passive_lacp.sh \
  bond_ipsec_offload.sh \
  bond_lacp_prio.sh

Note: A way to reduce such conflicts in the future is to sort each entry
by alphabetical order instead of adding new ones at the end. Same in the
'config' file that is also modified in this patch.

Rerere cache is available in [2].

1: https://github.com/multipath-tcp/mptcp_net-next/commit/f6c62892b853
2: https://github.com/multipath-tcp/mptcp-upstream-rr-cache/commit/65a75

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.

[-- Attachment #2: f6c62892b853cd5ddc6d4ceb41e732bc2e0d0c12.patch --]
[-- Type: text/x-patch, Size: 461 bytes --]

diff --cc tools/testing/selftests/drivers/net/bonding/Makefile
index 3462783ed3ac,c13ef40e7db1..f984d7dbba0a
--- a/tools/testing/selftests/drivers/net/bonding/Makefile
+++ b/tools/testing/selftests/drivers/net/bonding/Makefile
@@@ -12,7 -12,7 +12,8 @@@ TEST_PROGS := 
  	bond-eth-type-change.sh \
  	bond_macvlan_ipvlan.sh \
  	bond_passive_lacp.sh \
 -	bond_ipsec_offload.sh
++	bond_ipsec_offload.sh \
 +	bond_lacp_prio.sh
  
  TEST_FILES := \
  	lag_lib.sh \

  reply	other threads:[~2025-10-01  8:37 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   ` Matthieu Baerts [this message]
2025-10-02  1:20     ` [PATCHv3 net 2/2] selftests: bonding: add ipsec offload test: manual merge Hangbin Liu
2025-09-30  8:20 ` [PATCHv3 net 1/2] bonding: fix xfrm offload feature setup on active-backup mode patchwork-bot+netdevbpf

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=f4f61cb1-a2f5-4105-b051-0b16427fb12b@kernel.org \
    --to=matttbe@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=broonie@kernel.org \
    --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=sfr@canb.auug.org.au \
    --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