From: Matthieu Baerts <matttbe@kernel.org>
To: Mat Martineau <martineau@kernel.org>
Cc: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net] selftests: mptcp: join: fix local endp not being tracked
Date: Mon, 26 Jan 2026 19:27:00 +0100 [thread overview]
Message-ID: <d0e6f49a-1ee3-4cfd-8e46-ceb657f7a8dc@kernel.org> (raw)
In-Reply-To: <d75df364-38c3-b9b3-b978-dcba2b9fb96b@kernel.org>
Hi Mat,
On 14/01/2026 17:50, Mat Martineau wrote:
> On Mon, 22 Dec 2025, Matthieu Baerts (NGI0) wrote:
>
>> When running this mptcp_join.sh selftest on older kernel versions not
>> supporting local endpoints tracking, this test fails because 3 MP_JOIN
>> ACKs have been received, while only 2 were expected.
>>
>> It is not clear why only 2 MP_JOIN ACKs were expected on old kernel
>> versions, while 3 MP_JOIN SYN and SYN+ACK were expected. When testing on
>> the v5.15.197 kernel, 3 MP_JOIN ACKs are seen, which is also what is
>> expected in the selftests included in this kernel version, see commit
>> f4480eaad489 ("selftests: mptcp: add missing join check").
>>
>> Switch the expected MP_JOIN ACKs to 3. While at it, move this
>> chk_join_nr helper out of the special condition for older kernel
>> versions as it is now the same as with more recent ones. Also, invert
>> the condition to be more logical: what's expected on newer kernel
>> versions having such helper first.
>>
>> Fixes: d4c81bbb8600 ("selftests: mptcp: join: support local endpoint
>> being tracked or not")
>> Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
>
> Looks good to me, thanks Matthieu.
>
> Reviewed-by: Mat Martineau <martineau@kernel.org>
Thank you for the review!
Now in our tree:
New patches for t/upstream-net and t/upstream:
- b799002f1f8e: selftests: mptcp: join: fix local endp not being tracked
- Results: fb96b304d88a..af4181f61c9c (export-net)
- Results: ba44c0dbd2e9..b8bb952910af (export)
Tests are now in progress:
- export-net:
https://github.com/multipath-tcp/mptcp_net-next/commit/7ad24eb2a484fcd7d6e9d6d8d3285c917abc6354/checks
- export:
https://github.com/multipath-tcp/mptcp_net-next/commit/fce2d92251d9288da07c20f381ec436d24b0e2ee/checks
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-01-26 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 16:48 [PATCH mptcp-net] selftests: mptcp: join: fix local endp not being tracked Matthieu Baerts (NGI0)
2026-01-14 16:50 ` Mat Martineau
2026-01-26 18:27 ` Matthieu Baerts [this message]
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=d0e6f49a-1ee3-4cfd-8e46-ceb657f7a8dc@kernel.org \
--to=matttbe@kernel.org \
--cc=martineau@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