selftests: mptcp: explicitly trigger the listener diag code-path
authorPaolo Abeni <pabeni@redhat.com>
Fri, 23 Feb 2024 16:14:20 +0000 (17:14 +0100)
committerJakub Kicinski <kuba@kernel.org>
Tue, 27 Feb 2024 02:41:56 +0000 (18:41 -0800)
commitb4b51d36bbaa3ddb93b3e1ca3a1ef0aa629d6521
tree5ab9c6c0b8895230095a4419b60babd6c38c0766
parentd6a9608af9a75d13243d217f6ce1e30e57d56ffe
selftests: mptcp: explicitly trigger the listener diag code-path

The mptcp diag interface already experienced a few locking bugs
that lockdep and appropriate coverage have detected in advance.

Let's add a test-case triggering the relevant code path, to prevent
similar issues in the future.

Be careful to cope with very slow environments.

Note that we don't need an explicit timeout on the mptcp_connect
subprocess to cope with eventual bug/hang-up as the final cleanup
terminating the child processes will take care of that.

Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Reviewed-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Reviewed-by: Simon Horman <horms@kernel.org>
Link: https://lore.kernel.org/r/20240223-upstream-net-20240223-misc-fixes-v1-10-162e87e48497@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
tools/testing/selftests/net/mptcp/diag.sh