MPTCP Linux Development
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 1/3] Squash to "selftests: mptcp: remove add_addr_timeout settings"
Date: Wed, 03 Sep 2025 17:19:27 +0800	[thread overview]
Message-ID: <c5e62f971d89fabcae32ee2b924b5d6f34e2934b.camel@kernel.org> (raw)
In-Reply-To: <20250902-sft-mptcp-join-add_addr-no-retrans-v1-1-956a315d6a5a@kernel.org>

Hi Matt,

On Tue, 2025-09-02 at 21:01 +0200, Matthieu Baerts (NGI0) wrote:
> This reverts the patch: when add_addr_timeout is set to 1,
> chk_add_nr()
> and chk_add_tx_nr() are more tolerant with retransmissions, see
> commit
> 6ef84b1517e0 ("selftests: mptcp: more robust signal race test").
> 
> But the main reason is that this revert breaks the selftests running
> on
> old kernels.
> 
> It is then important to keep this. Plus it still acts as a maximum,
> just
> in case everything is very slow, we still have retransmissions in
> time,
> especially with the new exponential backoff.
> 
> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>

I agree.

Reviewed-by: Geliang Tang <geliang@kernel.org>

Thanks,
-Geliang

> ---
>  tools/testing/selftests/net/mptcp/mptcp_join.sh | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index
> a97b568104bc284f050b2f0e09fe3fdd3341c5cb..2f046167a0b6cc6fb5531a033d8
> d95c9ea399cf9 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> @@ -358,6 +358,8 @@ reset_with_add_addr_timeout()
>  		tables="${ip6tables}"
>  	fi
>  
> +	ip netns exec $ns1 sysctl -q net.mptcp.add_addr_timeout=1
> +
>  	if ! ip netns exec $ns2 $tables -A OUTPUT -p tcp \
>  			-m tcp --tcp-option 30 \
>  			-m bpf --bytecode \
> @@ -2303,6 +2305,7 @@ signal_address_tests()
>  		pm_nl_add_endpoint $ns2 10.0.4.2 flags signal
>  
>  		# the peer could possibly miss some addr
> notification, allow retransmission
> +		ip netns exec $ns1 sysctl -q
> net.mptcp.add_addr_timeout=1
>  		speed=slow \
>  			run_tests $ns1 $ns2 10.0.1.1
>  

  reply	other threads:[~2025-09-03  9:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 19:01 [PATCH mptcp-next 0/3] mptcp: fixes for adaptive ADD_ADDR retransmission timeout Matthieu Baerts (NGI0)
2025-09-02 19:01 ` [PATCH mptcp-next 1/3] Squash to "selftests: mptcp: remove add_addr_timeout settings" Matthieu Baerts (NGI0)
2025-09-03  9:19   ` Geliang Tang [this message]
2025-09-02 19:01 ` [PATCH mptcp-next 2/3] selftests: mptcp: join: tolerate more ADD_ADDR Matthieu Baerts (NGI0)
2025-09-04  9:26   ` Geliang Tang
2025-09-04 10:47     ` Matthieu Baerts
2025-09-04 11:27       ` Matthieu Baerts
2025-09-02 19:01 ` [PATCH mptcp-next 3/3] selftests: mptcp: join: allow more time to send ADD_ADDR Matthieu Baerts (NGI0)
2025-09-03  9:49   ` Geliang Tang
2025-09-02 21:08 ` [PATCH mptcp-next 0/3] mptcp: fixes for adaptive ADD_ADDR retransmission timeout MPTCP CI

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c5e62f971d89fabcae32ee2b924b5d6f34e2934b.camel@kernel.org \
    --to=geliang@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox