From: gang.yan@linux.dev
To: "Matthieu Baerts" <matttbe@kernel.org>, mptcp@lists.linux.dev
Cc: "Gang Yan" <yangang@kylinos.cn>
Subject: Re: [PATCH mptcp-next 1/2] selftests: mptcp: run fail_test in main shell during join test
Date: Fri, 24 Jul 2026 10:01:12 +0000 [thread overview]
Message-ID: <702d8cbc3ca44321c1020d059cc0007bb297841d@linux.dev> (raw)
In-Reply-To: <eb6d7e10-8631-41ff-9c66-80362193897f@kernel.org>
July 24, 2026 at 5:48 PM, "Matthieu Baerts" <matttbe@kernel.org mailto:matttbe@kernel.org?to=%22Matthieu%20Baerts%22%20%3Cmatttbe%40kernel.org%3E > wrote:
>
> On 24/07/2026 11:39, gang.yan@linux.dev wrote:
>
> >
> > July 24, 2026 at 5:28 PM, "Matthieu Baerts" <matttbe@kernel.org mailto:matttbe@kernel.org?to=%22Matthieu%20Baerts%22%20%3Cmatttbe%40kernel.org%3E > wrote:
> >
> >
> >
> > >
> > > Hi Gang,
> > >
> > > On 24/07/2026 08:52, Gang Yan wrote:
> > >
> > From: Gang Yan <yangang@kylinos.cn>
> >
> > check_transfer() compares the input and output files byte-by-byte using
> > `cmp -l "$in" "$out" | while read ...`. Because the while-loop body runs
> > in a subshell (the script sets neither lastpipe nor pipefail), the
> > fail_test call inside it -- which sets the global ret/last_test_failed --
> > and the `return 1` both act on the subshell, not on check_transfer().
> > check_transfer() thus always falls through to `return 0`, and any data
> > corruption affecting only the payload (leaving the subflow/PM counters
> > untouched) is silently reported as PASS.
> >
> > >
> > > Good catch!
> > >
> > > This looks like a fix that should be backported. Do you have a Fixes tag
> > > to add here?
> > >
> >
> > Hi Matt,
> >
> > Sorry for that, I originally thought only commits touching ./net/mptcp needed
> > a Fixes tag. This fix should be:
> >
> "Important" selftests fixes don't need to wait by going to the next
> version. If they fix something that can help users and/or CI, they are
> as essential as fixes in net/mptcp.
>
> We should just avoid fixes that don't affect results, e.g. the second
> patch of this series. But that's also valid for fixes in net/mptcp, e.g.
> a fix for a condition that can never happen with the current code, but
> will be the case with pending new features.
>
Thank you for your kind reminder. :)
Cherrs
Gang
> >
> > Fixes: 8117dac3e7c3 ("selftests: mptcp: add invert check in check_transfer")
> >
> Thanks!
>
> Cheers,
> Matt
> --
> Sponsored by the NGI0 Core fund.
>
next prev parent reply other threads:[~2026-07-24 10:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 6:52 [PATCH mptcp-next 0/2] selftests: mptcp: some improvement for selftests Gang Yan
2026-07-24 6:52 ` [PATCH mptcp-next 1/2] selftests: mptcp: run fail_test in main shell during join test Gang Yan
2026-07-24 9:28 ` Matthieu Baerts
2026-07-24 9:39 ` gang.yan
2026-07-24 9:48 ` Matthieu Baerts
2026-07-24 10:01 ` gang.yan [this message]
2026-07-24 10:02 ` Matthieu Baerts
2026-07-24 6:52 ` [PATCH mptcp-next 2/2] selftests: mptcp: simult_flows: set EXIT trap earlier Gang Yan
2026-07-24 9:27 ` Matthieu Baerts
2026-07-24 9:52 ` gang.yan
2026-07-24 10:01 ` Matthieu Baerts
2026-07-24 7:53 ` [PATCH mptcp-next 0/2] selftests: mptcp: some improvement for selftests 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=702d8cbc3ca44321c1020d059cc0007bb297841d@linux.dev \
--to=gang.yan@linux.dev \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=yangang@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.