From: Geliang Tang <geliang@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: MPTCP Linux <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-net v2 0/6] selftests: mptcp: join: fix flaky tests
Date: Wed, 05 Nov 2025 13:57:31 +0800 [thread overview]
Message-ID: <cc7e81692dbcdf2f16b2320ab93431ca0f22b2d6.camel@kernel.org> (raw)
In-Reply-To: <c2cd46563de5a4e90a95f98913d42cd198757167.camel@kernel.org>
On Wed, 2025-11-05 at 10:00 +0800, Geliang Tang wrote:
> Hi Matt,
>
> On Tue, 2025-11-04 at 13:10 +0100, Matthieu Baerts wrote:
> > Hi Geliang,
> >
> > On 02/11/2025 12:30, Matthieu Baerts (NGI0) wrote:
> > > When looking at the recent CI results on NIPA and MPTCP CIs, a
> > > few
> > > MPTCP
> > > Join tests are marked as unstable. Here are some fixes for that.
> > >
> > > - Patch 1: a small fix for mptcp_connect.sh, printing a note as
> > > initially intended. For >=v5.13.
> > >
> > > - Patch 2: avoid unexpected reset when closing subflows. For >=
> > > 5.13.
> > >
> > > - Patches 3-4: longer transfer when not waiting for the end. For
> > > > =5.18.
> > >
> > > - Patch 5: drop noisy plain RST packets when looking for
> > > MP_FASTCLOSE.
> > > For >= 5.18.
> > >
> > > - Patch 6: read all received data when expecting a reset. For >=
> > > v6.1.
> > >
> > > When reviewing patches 2-6, please double check that I'm not
> > > hiding
> > > real
> > > issues by tweaking the tests suite.
> >
> > (More eyes are welcome, especially on patch 5/6!)
>
> I tested patch 5/6 again and found that only dropping the plain RST
> from ns1 is sufficient to make it work. There is no need to
Oops, the test of only dropping ns1's plain RST failed after dozens of
loops.
> simultaneously drop the plain RST from ns2. What do you think?
So we do need to drop both ns1's and ns2's plain RST simultaneously, as
done in patch 5/6.
Thanks,
-Geliang
>
> If you agree, I can send a squash-to patch to fix it.
>
> Thanks,
> -Geliang
>
> >
> > Thank you for the review! Now in our tree:
> >
> > New patches for t/upstream-net and t/upstream:
> > - a9a49f5a022a: selftests: mptcp: connect: fix fallback note due to
> > OoO
> > - 818251a0fc51: selftests: mptcp: join: rm: set backup flag
> > - f0864a03b80b: selftests: mptcp: join: endpoints: longer transfer
> > - a68bf9260dab: selftests: mptcp: join: userspace: longer transfer
> > - 69569761c0f6: selftests: mptcp: join: fastclose: drop plain RST
> > - e99b7db5862e: selftests: mptcp: connect: trunc: read all recv
> > data
> > - Results: 3cf18f92ab22..09c25f9f5ca3 (export-net)
> > - Results: b35f4b01c8d3..625ded86ead5 (export)
> >
> > Tests are now in progress:
> >
> > - export-net:
> > https://github.com/multipath-tcp/mptcp_net-next/commit/c8f9b6716c62042010e0e231a789467236c55625/checks
> > - export:
> > https://github.com/multipath-tcp/mptcp_net-next/commit/31b5d615cdeb4fd6ea58fcd577b48543dd3b0617/checks
> >
> > Cheers,
> > Matt
>
>
prev parent reply other threads:[~2025-11-05 5:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 11:30 [PATCH mptcp-net v2 0/6] selftests: mptcp: join: fix flaky tests Matthieu Baerts (NGI0)
2025-11-02 11:30 ` [PATCH mptcp-net v2 1/6] selftests: mptcp: connect: fix fallback note due to OoO Matthieu Baerts (NGI0)
2025-11-04 5:53 ` Geliang Tang
2025-11-02 11:30 ` [PATCH mptcp-net v2 2/6] selftests: mptcp: join: rm: set backup flag Matthieu Baerts (NGI0)
2025-11-04 6:06 ` Geliang Tang
2025-11-04 6:57 ` Matthieu Baerts
2025-11-04 7:29 ` Geliang Tang
2025-11-04 8:47 ` Matthieu Baerts
2025-11-04 8:47 ` Matthieu Baerts
2025-11-02 11:30 ` [PATCH mptcp-net v2 3/6] selftests: mptcp: join: endpoints: longer transfer Matthieu Baerts (NGI0)
2025-11-02 11:30 ` [PATCH mptcp-net v2 4/6] selftests: mptcp: join: userspace: " Matthieu Baerts (NGI0)
2025-11-02 11:30 ` [PATCH mptcp-net v2 5/6] selftests: mptcp: join: fastclose: drop plain RST Matthieu Baerts (NGI0)
2025-11-03 7:16 ` Geliang Tang
2025-11-02 11:30 ` [PATCH mptcp-net v2 6/6] selftests: mptcp: connect: trunc: read all recv data Matthieu Baerts (NGI0)
2025-11-03 7:13 ` Geliang Tang
2025-11-03 12:12 ` Matthieu Baerts
2025-11-04 5:56 ` Geliang Tang
2025-11-02 12:33 ` [PATCH mptcp-net v2 0/6] selftests: mptcp: join: fix flaky tests MPTCP CI
2025-11-03 11:57 ` MPTCP CI
2025-11-04 7:30 ` Geliang Tang
2025-11-04 12:10 ` Matthieu Baerts
2025-11-05 2:00 ` Geliang Tang
2025-11-05 5:57 ` Geliang Tang [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=cc7e81692dbcdf2f16b2320ab93431ca0f22b2d6.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