All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next] Squash to "selftests/bpf: Add mptcp subflow subtest"
Date: Sat, 11 May 2024 15:50:29 +0200 (GMT+02:00)	[thread overview]
Message-ID: <45e113c1-7c33-4380-b85c-56dcb9048a73@kernel.org> (raw)
In-Reply-To: <48d243a507dc8b48932df4995ff98e5ec056e733.1715424100.git.tanggeliang@kylinos.cn>

Hi Geliang,

Thank you for this fix!

11 May 2024 12:42:08 Geliang Tang <geliang@kernel.org>:

> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Add pm_nl_ctl.
> Use SYS_NOFAIL in _ss_search().
>
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> ---
> tools/testing/selftests/bpf/Makefile           |  2 +-
> tools/testing/selftests/bpf/pm_nl_ctl.c        |  1 +
> tools/testing/selftests/bpf/prog_tests/mptcp.c | 15 ++++-----------
> 3 files changed, 6 insertions(+), 12 deletions(-)
> create mode 120000 tools/testing/selftests/bpf/pm_nl_ctl.c
>
> diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile
> index b90c718218ae..bd2e3b138a5c 100644
> --- a/tools/testing/selftests/bpf/Makefile
> +++ b/tools/testing/selftests/bpf/Makefile
> @@ -131,7 +131,7 @@ TEST_GEN_PROGS_EXTENDED = test_sock_addr test_skb_cgroup_id_user \
>     flow_dissector_load test_flow_dissector test_tcp_check_syncookie_user \
>     test_lirc_mode2_user xdping test_cpp runqslower bench bpf_testmod.ko \
>     xskxceiver xdp_redirect_multi xdp_synproxy veristat xdp_hw_metadata \
> -   xdp_features bpf_test_no_cfi.ko
> +   xdp_features bpf_test_no_cfi.ko pm_nl_ctl
>
> TEST_GEN_FILES += liburandom_read.so urandom_read sign-file uprobe_multi
>
> diff --git a/tools/testing/selftests/bpf/pm_nl_ctl.c b/tools/testing/selftests/bpf/pm_nl_ctl.c
> new file mode 120000
> index 000000000000..5a08c255b278
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/pm_nl_ctl.c

Best to prefix it with "mptcp_": clearer and it will be linked to MPTCP in the maintainers file.

> @@ -0,0 +1 @@
> +../net/mptcp/pm_nl_ctl.c
> \ No newline at end of file
> diff --git a/tools/testing/selftests/bpf/prog_tests/mptcp.c b/tools/testing/selftests/bpf/prog_tests/mptcp.c
> index 793b4b9c2bd2..9c6d1e4f6f35 100644
> --- a/tools/testing/selftests/bpf/prog_tests/mptcp.c
> +++ b/tools/testing/selftests/bpf/prog_tests/mptcp.c
> @@ -362,7 +362,8 @@ static int endpoint_init(char *flags)
>     SYS(fail, "ip -net %s link set dev veth1 up", NS_TEST);
>     SYS(fail, "ip -net %s addr add %s/24 dev veth2", NS_TEST, ADDR_2);
>     SYS(fail, "ip -net %s link set dev veth2 up", NS_TEST);
> -   SYS(fail, "ip -net %s mptcp endpoint add %s %s", NS_TEST, ADDR_2, flags);
> +   if (SYS_NOFAIL("ip -net %s mptcp endpoint add %s %s", NS_TEST, ADDR_2, flags))

It is maybe better to only use mptcp_pm_nl_ctl here: to maintain one way here, our CI will do the same as what the BPF one will do, and we avoid errors printed in stderr if "ip mptcp" is not supported.

> +       SYS(fail, "ip netns exec %s ./pm_nl_ctl add %s flags %s", NS_TEST, ADDR_2, flags);
>
>     return 0;
> fail:
> @@ -371,16 +372,8 @@ static int endpoint_init(char *flags)
>
> static int _ss_search(char *src, char *dst, char *port, char *keyword)
> {
> -   char cmd[128];
> -   int n;
> -
> -   n = snprintf(cmd, sizeof(cmd),
> -            "ip netns exec %s ss -Menita src %s dst %s %s %d | grep -q '%s'",
> -            NS_TEST, src, dst, port, PORT_1, keyword);
> -   if (n < 0 || n >= sizeof(cmd))
> -       return -1;
> -
> -   return system(cmd);
> +   return SYS_NOFAIL("ip netns exec %s ss -Menita src %s dst %s %s %d | grep -q '%s'",
> +             NS_TEST, src, dst, port, PORT_1, keyword);

If "ip mptcp" is not supported, I guess "ss -M" will not be supported as well, no?

Do we need -M here for these tests?

Cheers,
Matt

> }
>
> static int ss_search(char *src, char *keyword)
> --
> 2.43.0


  parent reply	other threads:[~2024-05-11 13:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-11 10:41 [PATCH mptcp-next] Squash to "selftests/bpf: Add mptcp subflow subtest" Geliang Tang
2024-05-11 11:34 ` MPTCP CI
2024-05-11 13:50 ` Matthieu Baerts [this message]
2024-05-11 23:17   ` Geliang Tang
2024-05-12  9:14     ` Matthieu Baerts
2024-05-12 11:45       ` Geliang Tang
2024-05-12 12:42         ` Matthieu Baerts
  -- strict thread matches above, loose matches on Subject: below --
2024-07-25  1:58 Geliang Tang
2024-07-25  2:47 ` MPTCP CI
2024-07-26  9:18 ` Matthieu Baerts
2024-07-27  1:12   ` Geliang Tang
2024-08-01 10:51     ` Matthieu Baerts
2024-09-07  3:45 Geliang Tang
2024-09-07  4:38 ` MPTCP CI
2024-09-09  1:59 ` Geliang Tang
2024-09-10 15:29 Matthieu Baerts (NGI0)

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=45e113c1-7c33-4380-b85c-56dcb9048a73@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@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.