summaryrefslogtreecommitdiff
path: root/tools/testing
diff options
context:
space:
mode:
authorDragos Tatulea <dtatulea@nvidia.com>2026-03-05 11:04:45 +0300
committerJakub Kicinski <kuba@kernel.org>2026-03-07 02:36:37 +0300
commit507ccb668f2db1377defdc54068eab3398bd5974 (patch)
tree6020b08881deaf6c327e696829f7745c707f2e2f /tools/testing
parent1a9940317c1b46b7641af6b4b14c9d2509ac88b2 (diff)
downloadlinux-507ccb668f2db1377defdc54068eab3398bd5974.tar.xz
selftests: drv-net: iou-zcrx: wait for memory cleanup of probe run
The large chunks test does a probe run of iou-zcrx before it runs the actual test. After the probe run finishes, the context will still exist until the deferred io_uring teardown. When running iou-zcrx the second time, io_uring_register_ifq() can return -EEXIST due to the existence of the old context. The fix is simple: wait for the context teardown using the new mp_clear_wait() utility before running the second instance of iou-zcrx. Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com> Link: https://patch.msgid.link/20260305080446.897628-2-dtatulea@nvidia.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/testing')
-rwxr-xr-xtools/testing/selftests/drivers/net/hw/iou-zcrx.py1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/testing/selftests/drivers/net/hw/iou-zcrx.py b/tools/testing/selftests/drivers/net/hw/iou-zcrx.py
index 66dd496ec5cf..e81724cb5542 100755
--- a/tools/testing/selftests/drivers/net/hw/iou-zcrx.py
+++ b/tools/testing/selftests/drivers/net/hw/iou-zcrx.py
@@ -151,6 +151,7 @@ def test_zcrx_large_chunks(cfg) -> None:
if probe.ret == SKIP_CODE:
raise KsftSkipEx(probe.stdout.strip())
+ mp_clear_wait(cfg)
with bkg(rx_cmd, exit_wait=True):
wait_port_listen(cfg.port, proto="tcp")
cmd(tx_cmd, host=cfg.remote)