Matthieu Baerts 972ba596e7 selftests: mptcp: run mptcp_sockopt from a new netns ... [ Upstream commit 7e68d31020 ] Not running it from a new netns causes issues if some MPTCP settings are modified, e.g. if MPTCP is disabled from the sysctl knob, if multiple addresses are available and added to the MPTCP path-manager, etc. In these cases, the created connection will not behave as expected, e.g. unable to create an MPTCP socket, more than one subflow is seen, etc. A new "sandbox" net namespace is now created and used to run mptcp_sockopt from this controlled environment. Fixes: ce9979129a ("selftests: mptcp: add mptcp getsockopt test cases") Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net> Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com> Signed-off-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>		2022-12-02 17:43:03 +01:00
..
crypto/chacha20-s390	tools/testing/crypto: Use vzalloc instead of vmalloc+memset	2022-07-05 14:46:36 +02:00
cxl	tools/testing/cxl: Fix some error exits	2022-11-26 09:27:21 +01:00
fault-injection
ktest
kunit	kunit: tool: Enable virtio/PCI by default on UML	2022-07-08 11:22:29 -06:00
memblock	memblock updates for v5.20	2022-08-09 09:48:30 -07:00
nvdimm	ndtest: Cleanup all of blk namespace specific code	2022-07-12 17:57:55 -07:00
radix-tree	tools: Add kmem_cache_alloc_lru()	2022-04-22 14:24:28 -04:00
scatterlist
selftests	selftests: mptcp: run mptcp_sockopt from a new netns	2022-12-02 17:43:03 +01:00
vsock