]> git.ipfire.org Git - thirdparty/kernel/linux.git/commit
selftests: mptcp: get stats just before timing out
authorMatthieu Baerts (NGI0) <matttbe@kernel.org>
Fri, 14 Nov 2025 18:12:12 +0000 (19:12 +0100)
committerJakub Kicinski <kuba@kernel.org>
Tue, 18 Nov 2025 03:27:47 +0000 (19:27 -0800)
commiteea2f44870d297f0535944bf4dbf49d8b90c838e
tree6803832d1ff58cc212f8dc40efb3c283f7b4f4a1
parent39348f5f2f13c2da122b5049952066c2e802d3a0
selftests: mptcp: get stats just before timing out

Recently, some debugging happened around a test that was timing out. The
stats were showing connections being closed which was confusing because
the closing state was caused by the timeout stopping the transfer.

To avoid such confusion, the timeout is no longer done per mptcp_connect
process, but separately. In case of timeout, the stats are now printed,
then the apps are killed.

The stats will still be printed after the kill, but that's fine, and
this might even be useful, just in case. Timeout should be exceptional.

Reviewed-by: Geliang Tang <geliang@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Link: https://patch.msgid.link/20251114-net-next-mptcp-sft-count-cache-stats-timeout-v1-8-863cb04e1b7b@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
tools/testing/selftests/net/mptcp/mptcp_connect.sh
tools/testing/selftests/net/mptcp/mptcp_join.sh
tools/testing/selftests/net/mptcp/mptcp_lib.sh
tools/testing/selftests/net/mptcp/mptcp_sockopt.sh
tools/testing/selftests/net/mptcp/simult_flows.sh