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 1/2] selftests: mptcp: join: fix 'delete and re-add' test
Date: Tue, 27 Jun 2023 15:25:56 +0200 [thread overview]
Message-ID: <ZJrjZJ4qc5sMyr75@renaissance-vector> (raw)
In-Reply-To: <94a77161-2299-e470-c0d5-c14cf828cd92@tessares.net>
On Mon, Jun 26, 2023 at 01:31:07PM +0200, Matthieu Baerts wrote:
> Hi Andrea,
Hi Matthieu,
Thanks for your review.
>
> On 23/06/2023 14:19, Andrea Claudi wrote:
> > mptcp_join '002 delete and re-add' test currently fails in the 'after
> > delete' testcase.
>
> I guess it only fails if you use "-i" option to use "ip mptcp" instead
> of "pm_nl_ctl", right?
>
Yes, exactly.
> MPTCP CI doesn't launch the tests with the "-i" option.
>
> Can you mention that it fails only when using "ip mptcp" which is not
> the default mode please? It might be good to include that in the title
> too not to think the test is broken and the CI didn't complain about that.
>
Sure, will do that.
> BTW, how did you launch mptcp_join.sh selftest to have this test
> launched as second position ("002")? With "-Ii"?
>
Yes, that's exactly the case, I use "./mptcp_join.sh -I -i"
> (you can remove this "002": it is specific to the way you launched the
> test, not using the default mode)
Will do.
>
> > This happens because endpoint delete includes an ip address while id is
> > not 0, contrary to what is indicated in the ip mptcp man page:
> >
> > "When used with the delete id operation, an IFADDR is only included when
> > the ID is 0."
> >
> > This fixes the issue simply not using the $addr variable in
> > pm_nl_del_endpoint().
>
> If you do that, are you not going to break other tests? e.g.
> - "remove id 0 subflow"
> - "remove id 0 address"
>
> (I didn't check all possibilities, maybe not or maybe there are others)
>
> Because if you specify the ID 0, you do need to specify the address, no?
>
That's right, of course. I'll fix that in v2 and make sure no other
tests are impacted with a "mptcp_join.sh -i" run.
> > Fixes: 34aa6e3bccd8 ("selftests: mptcp: add ip mptcp wrappers")
> > Signed-off-by: Andrea Claudi <aclaudi@redhat.com>
> > ---
> > tools/testing/selftests/net/mptcp/mptcp_join.sh | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > index 0ae8cafde439..5424dcacfffa 100755
> > --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> > @@ -678,7 +678,7 @@ pm_nl_del_endpoint()
> > local addr=$3
> >
> > if [ $ip_mptcp -eq 1 ]; then
> > - ip -n $ns mptcp endpoint delete id $id $addr
> > + ip -n $ns mptcp endpoint delete id $id
>
> Should you not add "${addr}" only if ${id} == 1?
>
> > else
> > ip netns exec $ns ./pm_nl_ctl del $id $addr
> > fi
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
>
next prev parent reply other threads:[~2023-06-27 13:26 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 [this message]
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
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=ZJrjZJ4qc5sMyr75@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).