diff options
author | 2023-06-08 18:38:52 +0200 | |
---|---|---|
committer | 2023-06-10 00:02:16 -0700 | |
commit | c6f7eccc519837ebde1d099d9610c4f1d5bd975e (patch) | |
tree | 24ca80c8491bd7300026bfab732ccc5fe7ee32d3 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | selftests: mptcp: sockopt: relax expected returned size (diff) | |
download | wireguard-linux-c6f7eccc519837ebde1d099d9610c4f1d5bd975e.tar.xz wireguard-linux-c6f7eccc519837ebde1d099d9610c4f1d5bd975e.zip |
selftests: mptcp: sockopt: skip getsockopt checks if not supported
Selftests are supposed to run on any kernels, including the old ones not
supporting all MPTCP features.
One of them is the getsockopt(SOL_MPTCP) to get info about the MPTCP
connections introduced by commit 55c42fa7fa33 ("mptcp: add MPTCP_INFO
getsockopt") and the following ones.
It is possible to look for "mptcp_diag_fill_info" in kallsyms because
it is introduced by the mentioned feature. So we can know in advance if
the feature is supported and skip the sub-test if not.
Link: https://github.com/multipath-tcp/mptcp_net-next/issues/368
Fixes: ce9979129a0b ("selftests: mptcp: add mptcp getsockopt test cases")
Cc: stable@vger.kernel.org
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions