All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Claudi <aclaudi@redhat.com>
To: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com
Cc: mptcp@lists.linux.dev, matthieu.baerts@tessares.net,
	martineau@kernel.org, geliang.tang@suse.com
Subject: [PATCH net 0/2] selftests: fix mptcp_join test
Date: Fri, 23 Jun 2023 14:19:50 +0200	[thread overview]
Message-ID: <cover.1687522138.git.aclaudi@redhat.com> (raw)

This series fixes two mptcp_join testcases.
- '001 implicit EP' fails because of:
  - missing iproute support for mptcp 'implicit' flag, fixed with
    iproute2-next commit 3a2535a41854 ("mptcp: add support for implicit
    flag")
  - pm_nl_check_endpoint expecting two ip addresses, while only one is
    present in the iproute output;
- '002 delete and re-add' fails because the endpoint delete command
  provide both id and ip address, while address should be provided only
  if id is 0.

Andrea Claudi (2):
  selftests: mptcp: join: fix 'delete and re-add' test
  selftests: mptcp: join: fix 'implicit EP' test

 tools/testing/selftests/net/mptcp/mptcp_join.sh | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-06-23 12:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 12:19 Andrea Claudi [this message]
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-23 14:08   ` selftests: mptcp: join: fix 'implicit EP' test: Tests Results MPTCP CI
2023-06-26 11:32   ` [PATCH net 2/2] selftests: mptcp: join: fix 'implicit EP' test 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=cover.1687522138.git.aclaudi@redhat.com \
    --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 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.