From: Andrea Claudi <aclaudi@redhat.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mptcp@lists.linux.dev,
martineau@kernel.org, geliang.tang@suse.com
Subject: Re: [PATCH net 2/2] selftests: mptcp: join: fix 'implicit EP' test
Date: Tue, 27 Jun 2023 15:43:30 +0200 [thread overview]
Message-ID: <ZJrngsQIAI3ATrlU@renaissance-vector> (raw)
In-Reply-To: <30ecb04c-47b1-fdf8-d695-e9b9b2198319@tessares.net>
On Mon, Jun 26, 2023 at 01:32:17PM +0200, Matthieu Baerts wrote:
> Hi Andrea,
>
> On 23/06/2023 14:19, Andrea Claudi wrote:
> > mptcp_join '001 implicit EP' test currently fails because of two
> > reasons:
>
> Same as on patch 1/2: can you remove "001" and mention it is only
> failing when using "ip mptcp" ("-i" option) please?
>
Sure, no problem.
> > - iproute v6.3.0 does not support the implicit flag, fixed with
> > iproute2-next commit 3a2535a41854 ("mptcp: add support for implicit
> > flag")
>
> Thank you for that!
>
> Out of curiosity: why is it in iproute2-next (following net-next tree,
> for v6.5) and not in iproute2 tree (following -net / Linus tree: for v6.4)?
>
I usually target fixes to iproute2 and new stuff to iproute2-next, no
other reason than that. But I see your point here, having this on -net
may end up in the commit not landing in the same release cycle.
Should I send v2 for this series to mptcp-next, then?
Andrea
> > - pm_nl_check_endpoint wrongly expects the ip address to be repeated two
> > times in iproute output, and does not account for a final whitespace
> > in it.
> >
> > This fixes the issue trimming the whitespace in the output string and
> > removing the double address in the expected string.
> >
> > Fixes: 69c6ce7b6eca ("selftests: mptcp: add implicit endpoint test case")
> > Signed-off-by: Andrea Claudi <aclaudi@redhat.com>
> > ---
> > tools/testing/selftests/net/mptcp/mptcp_join.sh | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > index 5424dcacfffa..6c3525e42273 100755
> > --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > @@ -768,10 +768,11 @@ pm_nl_check_endpoint()
> > fi
> >
> > if [ $ip_mptcp -eq 1 ]; then
> > + # get line and trim trailing whitespace
> > line=$(ip -n $ns mptcp endpoint show $id)
> > + line="${line% }"
> > # the dump order is: address id flags port dev
> > - expected_line="$addr"
> > - [ -n "$addr" ] && expected_line="$expected_line $addr"
> > + [ -n "$addr" ] && expected_line="$addr"
> > expected_line="$expected_line $id"
> > [ -n "$_flags" ] && expected_line="$expected_line ${_flags//","/" "}"
> > [ -n "$dev" ] && expected_line="$expected_line $dev"
>
> It looks good, no need to change anything here but later (not for -net
> anyway), we should probably parse the JSON output of "ip -j mptcp" instead.
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
>
next prev parent reply other threads:[~2023-06-27 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 12:19 [PATCH net 0/2] selftests: fix mptcp_join test Andrea Claudi
2023-06-23 12:19 ` [PATCH net 1/2] selftests: mptcp: join: fix 'delete and re-add' test Andrea Claudi
2023-06-26 11:31 ` Matthieu Baerts
2023-06-27 13:25 ` Andrea Claudi
2023-06-23 12:19 ` [PATCH net 2/2] selftests: mptcp: join: fix 'implicit EP' test Andrea Claudi
2023-06-26 11:32 ` Matthieu Baerts
2023-06-27 13:43 ` Andrea Claudi [this message]
2023-06-27 14:07 ` Matthieu Baerts
2023-06-26 11:28 ` [PATCH net 0/2] selftests: fix mptcp_join test Matthieu Baerts
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=ZJrngsQIAI3ATrlU@renaissance-vector \
--to=aclaudi@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang.tang@suse.com \
--cc=kuba@kernel.org \
--cc=martineau@kernel.org \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).