[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b536d171-11c-407b-4236-39fb592b571a@linux.intel.com>
Date: Fri, 18 Feb 2022 14:00:54 -0800 (PST)
From: Mat Martineau <mathew.j.martineau@...ux.intel.com>
To: netdev@...r.kernel.org
cc: Paolo Abeni <pabeni@...hat.com>, davem@...emloft.net,
kuba@...nel.org, matthieu.baerts@...sares.net,
geliang.tang@...e.com, mptcp@...ts.linux.dev
Subject: Re: [PATCH net 6/7] selftests: mptcp: more robust signal race test
On Fri, 18 Feb 2022, Mat Martineau wrote:
> From: Paolo Abeni <pabeni@...hat.com>
>
> The in kernel MPTCP PM implementation can process a single
> incoming add address option at any given time. In the
> mentioned test the server can surpass such limit. Let the
> setup cope with that allowing a faster add_addr retransmission.
>
Jakub / David -
A heads-up, this patch will give a trivial merge conflict in the hunk
below when merging net/master to net-next/master. It's only due to changes
in the preceeding context (those "ip netns exec" lines), so conflict
resolution will be obvious.
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index 10b3bd805ac6..0d6a71e7bb59 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
...
> @@ -1158,7 +1164,10 @@ signal_address_tests()
> ip netns exec $ns2 ./pm_nl_ctl add 10.0.2.2 flags signal
> ip netns exec $ns2 ./pm_nl_ctl add 10.0.3.2 flags signal
> ip netns exec $ns2 ./pm_nl_ctl add 10.0.4.2 flags signal
> - run_tests $ns1 $ns2 10.0.1.1
> +
> + # the peer could possibly miss some addr notification, allow retransmission
> + ip netns exec $ns1 sysctl -q net.mptcp.add_addr_timeout=1
> + run_tests $ns1 $ns2 10.0.1.1 0 0 0 slow
> chk_join_nr "signal addresses race test" 3 3 3
>
> # the server will not signal the address terminating
> --
> 2.35.1
>
>
--
Mat Martineau
Intel
Powered by blists - more mailing lists