netdev - Re: [PATCH net-next v8 16/16] selftests/net: Add netkit container tests

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] [day] [month] [year] [list]

Message-ID: <d7490f71-72ac-4c50-b848-c3d366e67a80@davidwei.uk>
Date: Mon, 2 Feb 2026 07:54:34 +0900
From: David Wei <dw@...idwei.uk>
To: Jakub Kicinski <kuba@...nel.org>, Daniel Borkmann <daniel@...earbox.net>
Cc: netdev@...r.kernel.org, bpf@...r.kernel.org, davem@...emloft.net,
 razor@...ckwall.org, pabeni@...hat.com, willemb@...gle.com, sdf@...ichev.me,
 john.fastabend@...il.com, martin.lau@...nel.org, jordan@...fe.io,
 maciej.fijalkowski@...el.com, magnus.karlsson@...el.com, toke@...hat.com,
 yangzhenze@...edance.com, wangdongdong.6@...edance.com
Subject: Re: [PATCH net-next v8 16/16] selftests/net: Add netkit container
 tests

On 2026-02-01 09:24, Jakub Kicinski wrote:
> On Thu, 29 Jan 2026 23:28:30 +0100 Daniel Borkmann wrote:
>> Add two tests using NetDrvContEnv. One basic test that sets up a netkit
>> pair, with one end in a netns. Use LOCAL_PREFIX_V6 and nk_forward BPF
>> program to ping from a remote host to the netkit in netns.
>>
>> Second is a selftest for netkit queue leasing, using io_uring zero copy
>> test binary inside of a netns with netkit. This checks that memory
>> providers can be bound against virtual queues in a netkit within a
>> netns that are leasing from a physical netdev in the default netns.
> 
> We should cover the uAPI and the tricky part of the handling please.
> 
> So off the top of my head main bits:
>   - the expected attributes on lessor and lessee via Netlink
>   - destroying the netkit with MP attached
>     - checking the state via YNL,
>     - attaching MP from the main dev to make sure we didn't leave
>       anything behind
>   - destroying phys dev while netkit exists (prolly netdevsim :S)
>   - making sure XDP can't be attached on phys dev when MP is installed
>     via netkit
> 
> ... whatever else you found to be tricky in the implementation.

Sounds good. I'll add these test cases and more.