netdev - Re: [PATCH net-next v1 2/7] selftests/net: add MemPrvEnv env

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251120191823.368addb5@kernel.org>
Date: Thu, 20 Nov 2025 19:18:23 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: David Wei <dw@...idwei.uk>
Cc: netdev@...r.kernel.org, Andrew Lunn <andrew+netdev@...n.ch>, "David S.
 Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
 Abeni <pabeni@...hat.com>, Daniel Borkmann <daniel@...earbox.net>
Subject: Re: [PATCH net-next v1 2/7] selftests/net: add MemPrvEnv env

On Wed, 19 Nov 2025 19:30:11 -0800 David Wei wrote:
> Memory provider HW selftests (i.e. zcrx, devmem) require setting up a
> netdev with e.g. flow steering rules. Add a new MemPrvEnv that sets up
> the test env, restoring it to the original state prior to the test. This
> also speeds up tests since each individual test case don't need to
> repeat the setup/teardown.

Hm, this feels a bit too specific to the particular use case.
I think we have a gap in terms of the Env classes for setting up
"a container" tests. Meaning - NetDrvEpEnv + an extra NetNs with
a netkit / veth.  init net gets set up to forward traffic to and
from the netkit / veth with BPF or routing. And the container
needs its own IP address from a new set of params.

I think that's the extent of the setup provided by the env.
We can then reuse the env for all "container+offload" cases.
The rest belongs in each test module.