From: Matthieu Baerts <matttbe@kernel.org>
To: GangYan <gang.yan@linux.dev>, mptcp@lists.linux.dev
Subject: Re: [RFC mptcp-next] selftests: mptcp: Add a test for self-conn fallback
Date: Thu, 14 Aug 2025 16:41:34 +0200 [thread overview]
Message-ID: <42d39ee7-1ff9-4e70-9aaa-6445e4e7da9e@kernel.org> (raw)
In-Reply-To: <aJ2k-JhkBmIAfdoX@yangang-ThinkPad-T14-Gen-1>
Hi Gang,
On 14/08/2025 10:57, GangYan wrote:
>> On Thu, Aug 14, 2025 at 08:51:13AM +0000, MPTCP CI wrote:
> Hi Matt,
>
> I noticed the 'MPTCP_MIB_SIMULTCONNFALLBACK' is not coverd by selftests
> through 'code_coverage'. So, I add a test according to issue#35, and I
> would like to seek your advice on the following points:
>
> -Is it suitable to add a test like this patch to cover this part of code?
> -If yes, please give me some feedback on modification suggestions about
> this patch.
Good idea to cover this.
My fear is that this test might be unstable, no?
Is it not easier to reproduce this with Packetdrill test? e.g.
> `../common/defaults.sh`
>
> 0 socket(..., SOCK_STREAM|SOCK_NONBLOCK, IPPROTO_MPTCP) = 3
> +0 connect(3, ..., ...) = -1 EINPROGRESS (Operation now in progress)
>
> +0 > S 0:0(0) <mss 1460, sackOK, TS val 100 ecr 0, nop, wscale 8, mpcapable v1 flags[flag_h] nokey>
> +0 < S 0:0(0) win 1000 <mss 1460, sackOK, TS val 407 ecr 0, nop, wscale 8, mpcapable v1 flags[flag_h] nokey>
> +0 > S. 0:0(0) ack 1 <mss 1460, sackOK, TS val 330 ecr 0, nop, wscale 8, mpcapable v1 flags[flag_h] nokey>
> +0 < S. 0:0(0) ack 1 win 65535 <mss 1460, sackOK, TS val 700 ecr 100, nop, wscale 8, mpcapable v1 flags[flag_h] key[skey=2]>
> +0 > . 1:1(0) ack 1 <nop, nop, TS val 845707014 ecr 700, nop, nop, sack 0:1>
Then check the MIB counter.
(Note: I didn't check, the alignment is not OK, just wrote it very quickly)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2025-08-14 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 6:58 [RFC mptcp-next] selftests: mptcp: Add a test for self-conn fallback Gang Yan
2025-08-14 8:51 ` MPTCP CI
2025-08-14 8:57 ` GangYan
2025-08-14 14:41 ` 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=42d39ee7-1ff9-4e70-9aaa-6445e4e7da9e@kernel.org \
--to=matttbe@kernel.org \
--cc=gang.yan@linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).