diff options
| author | Jakub Kicinski <kuba@kernel.org> | 2026-09-12 13:31:01 -0700 |
|---|---|---|
| committer | Paolo Abeni <pabeni@redhat.com> | 2026-09-15 15:18:56 +0200 |
| commit | b8e9e7d82e7eefd5d2d528469d94ec20e96b38c3 (patch) | |
| tree | bd7ebbb1f0d1876c6a18a6a1f6f3fc05736727f5 /include/uapi/linux/raid | |
| parent | 1a523f29fe4f663594926005714a3c10b9c04539 (diff) | |
| download | linux-next-b8e9e7d82e7eefd5d2d528469d94ec20e96b38c3.tar.gz linux-next-b8e9e7d82e7eefd5d2d528469d94ec20e96b38c3.zip | |
selftests: drv-net: devmem: set reuseaddr on the sender's source port
devmem.py fails on the HW runners with:
CMD[remote]: dd if=/dev/zero bs=512 count=1 2>/dev/null | socat -b 512 \
-u - TCP6:[fd00:2::1]:50051,bind=[fd00:2::2]:50051,nodelay
STDERR: socat[41018] W bind(5, {AF=10 [fd00:2::2]:50051}, 28): \
Address already in use
ncdevmem installs a 5-tuple flow rule which matches the source port, so
socat has to bind it explicitly. The port comes from rand_port(), which
checks availability on the DUT - but we bind on the remote...
That said the failure rate seems to high to be random collisions
(~2% per sub-test). It's probably TIME_WAIT sockets on the remote,
run_rx_hds() alone creates 12 of them.
Set reuseaddr so a TIME_WAIT socket does not fail the bind. Collisions
with a live socket are still possible, we'll see if they are frequent
enough to care.
Reviewed-by: Breno Leitao <leitao@debian.org>
Reviewed-by: Bobby Eshleman <bobbyeshleman@meta.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Link: https://patch.msgid.link/20260912203101.153688-1-kuba@kernel.org
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'include/uapi/linux/raid')
0 files changed, 0 insertions, 0 deletions
