From: Jakub Kicinski <kuba@kernel.org>
To: Feng Wang <wangfe@google.com>
Cc: netdev@vger.kernel.org, steffen.klassert@secunet.com,
antony.antony@secunet.com, leonro@nvidia.com
Subject: Re: [PATCH 2/2] selftests: rtnetlink: add ipsec packet offload test
Date: Mon, 4 Nov 2024 17:27:39 -0800 [thread overview]
Message-ID: <20241104172739.2993c325@kernel.org> (raw)
In-Reply-To: <20241104172612.6e5c1a14@kernel.org>
On Mon, 4 Nov 2024 17:26:12 -0800 Jakub Kicinski wrote:
> On Mon, 4 Nov 2024 15:33:15 -0800 Feng Wang wrote:
> > From: wangfe <wangfe@google.com>
> >
> > Duplicating kci_test_ipsec_offload to create a packet offload test.
> > Using the netdevsim as a device for testing ipsec packet mode.
> > Test the XFRM commands for setting up IPsec hardware packet offloads,
> > especially configuring the XFRM interface ID.
>
> CI appears to not be on board:
>
> # 26.29 [+0.07] RTNETLINK answers: Operation not supported
> # 26.36 [+0.07] FAIL: ipsec_packet_offload can't create SA
>
> https://netdev-3.bots.linux.dev/vmksft-net/results/846081/25-rtnetlink-sh/stdout
>
> Maybe you need to add more options to tools/testing/selftests/net/config
>
> But stepping back - I think it may be time to move the crypto tunnel
> tests based on netdevsim to
> tools/testing/selftests/drivers/net/netdevsim ? rtnetlink is our main
> netlink family, likely half of all our tests could be called a
> "rtnetlink test".
PS. this wiki tells you how the CI builds the kernel, so it is useful
for making sure the config options are chosen correctly:
https://github.com/linux-netdev/nipa/wiki/How-to-run-netdev-selftests-CI-style
next prev parent reply other threads:[~2024-11-05 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 23:33 [PATCH 2/2] selftests: rtnetlink: add ipsec packet offload test Feng Wang
2024-11-05 1:26 ` Jakub Kicinski
2024-11-05 1:27 ` Jakub Kicinski [this message]
2024-11-12 19:49 ` Feng Wang
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=20241104172739.2993c325@kernel.org \
--to=kuba@kernel.org \
--cc=antony.antony@secunet.com \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=wangfe@google.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).