linux/tools/testing/selftests/drivers
Jakub Kicinski bda053d644 selftests: drv-net: don't assume device has only 2 queues
The test is implicitly assuming the device only has 2 queues.
A real device will likely have more. The exact problem is that
because NAPIs get added to the list from the head, the netlink
dump reports them in reverse order. So the naive napis[0] will
actually likely give us the _last_ NAPI, not the first one.
Re-enable all the NAPIs instead of hard-coding 2 in the test.
This way the NAPIs we operated on will always reappear,
doesn't matter where they were in the registration order.

Fixes: e6d7626881 ("net: Update threaded state in napi config in netif_set_threaded")
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Joe Damato <joe@dama.to>
Link: https://patch.msgid.link/20250809001205.1147153-2-kuba@kernel.org
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
2025-08-12 14:43:05 +02:00
..
dma-buf selftests/udmabuf: add a test to pin first before writing to memfd 2025-07-09 22:42:15 -07:00
gpu
net selftests: drv-net: don't assume device has only 2 queues 2025-08-12 14:43:05 +02:00
ntsync selftests: ntsync: Add a stress test for contended waits. 2025-01-08 13:18:12 +01:00
platform/x86/intel/ifs
s390x/uvdevice selftests: harness: remove unneeded __constructor_order_last() 2024-08-06 13:40:20 -06:00
sdsi
usb/usbip
.gitignore