From: Geliang Tang <geliang@kernel.org>
To: "Matthieu Baerts (NGI0)" <matttbe@kernel.org>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 08/11] selftests: mptcp: join chk_stale_nr: avoid dup stats
Date: Sun, 28 Dec 2025 12:43:47 +0800 [thread overview]
Message-ID: <34fa8f6dc3cfe8a70cbb207e300d34719eea82b9.camel@kernel.org> (raw)
In-Reply-To: <f7bd1668def5a8062f7deef87b88a7444e037587.camel@kernel.org>
On Sun, 2025-12-28 at 10:25 +0800, Geliang Tang wrote:
> Hi Matt,
>
> Thanks for this patch.
>
> On Fri, 2025-12-26 at 07:40 +0100, Matthieu Baerts (NGI0) wrote:
> > nstat outputs are already printed when calling 'fail_test', no need
> > to
> > do it again.
> >
> > While at it, no need to use the dump_stats variable, print the
> > extra
> > stats directly. And use 'ip -n $ns' instead of 'ip netns exec $ns',
> > shorter and clearer.
> >
> > Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> > ---
> > tools/testing/selftests/net/mptcp/mptcp_join.sh | 10 ++--------
> > 1 file changed, 2 insertions(+), 8 deletions(-)
> >
> > diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > index 63a84a4d43a6..80e03168b419 100755
> > --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > @@ -1648,7 +1648,6 @@ chk_stale_nr()
> > local stale_min=$2
> > local stale_max=$3
> > local stale_delta=$4
> > - local dump_stats
> > local stale_nr
> > local recover_nr
> >
> > @@ -1664,16 +1663,11 @@ chk_stale_nr()
> > fail_test "got $stale_nr stale[s] $recover_nr
> > recover[s], " \
> > " expected stale in range
> > [$stale_min..$stale_max]," \
> > " stale-recover delta $stale_delta"
> > - dump_stats=1
> > + echo $ns stats
> > + ip -n $ns -s link show
> > else
> > print_ok
> > fi
> > -
> > - if [ "${dump_stats}" = 1 ]; then
> > - echo $ns stats
> > - ip netns exec $ns ip -s link show
> > - ip netns exec $ns nstat -as | grep MPTcp
>
> mptcp_lib_pr_nstat() is called in fail_test(), it's slightly
> different
> from the above line:
>
> ip netns exec "${ns}" nstat -as | grep Tcp
>
> So, is it necessary for us to keep the above line?
Sorry, I made a mistake. The output of 'grep Tcp' includes the output
of 'grep MPTcp', so the information of dump_stats is indeed redundant.
So this patch looks good to me.
Reviewed-by: Geliang Tang <geliang@kernel.org>
Thanks,
-Geliang
>
> Thanks,
> -Geliang
>
> > - fi
> > }
> >
> > chk_add_nr()
next prev parent reply other threads:[~2025-12-28 4:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 6:40 [PATCH mptcp-next 00/11] mptcp: avoid dup events + error + misc Matthieu Baerts (NGI0)
2025-12-26 6:40 ` [PATCH mptcp-next 01/11] mptcp: avoid dup SUB_CLOSED events after disconnect Matthieu Baerts (NGI0)
2026-01-04 3:15 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 02/11] selftests: mptcp: check no dup close events after error Matthieu Baerts (NGI0)
2026-01-04 3:17 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 03/11] mptcp: only reset subflow errors when propagated Matthieu Baerts (NGI0)
2026-01-04 3:30 ` Geliang Tang
2026-01-04 4:00 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 04/11] selftests: mptcp: check subflow errors in close events Matthieu Baerts (NGI0)
2025-12-26 6:40 ` [PATCH mptcp-next 05/11] selftests: mptcp: join: wait for estab event instead of MPJ Matthieu Baerts (NGI0)
2025-12-28 2:41 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 06/11] selftests: mptcp: join: fix wait_mpj helper Matthieu Baerts (NGI0)
2025-12-26 6:40 ` [PATCH mptcp-next 07/11] selftests: mptcp: join: userspace: wait for new events Matthieu Baerts (NGI0)
2025-12-28 2:48 ` Geliang Tang
2026-01-26 18:59 ` Matthieu Baerts
2025-12-26 6:40 ` [PATCH mptcp-next 08/11] selftests: mptcp: join chk_stale_nr: avoid dup stats Matthieu Baerts (NGI0)
2025-12-28 2:25 ` Geliang Tang
2025-12-28 4:43 ` Geliang Tang [this message]
2025-12-26 6:40 ` [PATCH mptcp-next 09/11] selftests: mptcp: join: avoid declaring i if not used Matthieu Baerts (NGI0)
2025-12-28 2:51 ` Geliang Tang
2025-12-26 6:40 ` [PATCH mptcp-next 10/11] selftests: mptcp: connect: fix maybe-uninitialize warn Matthieu Baerts (NGI0)
2025-12-28 2:54 ` Geliang Tang
2026-01-26 19:02 ` Matthieu Baerts
2025-12-26 6:40 ` [PATCH mptcp-next 11/11] selftests: mptcp: connect cleanup TFO setup Matthieu Baerts (NGI0)
2025-12-28 2:59 ` Geliang Tang
2025-12-26 7:51 ` [PATCH mptcp-next 00/11] mptcp: avoid dup events + error + misc 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=34fa8f6dc3cfe8a70cbb207e300d34719eea82b9.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