From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v15 4/7] selftests: mptcp: userspace pm remove initial subflow
Date: Thu, 12 Oct 2023 16:35:59 +0200 [thread overview]
Message-ID: <99e62e52-bbc1-4331-8f54-561cc207718b@kernel.org> (raw)
In-Reply-To: <f13919cfd0f090a63d05a9b3d7e769416a2c27d1.1697100600.git.geliang.tang@suse.com>
Hi Geliang,
On 12/10/2023 10:52, Geliang Tang wrote:
> This patch adds a selftest for userpsace PM to remove the initial
> subflow. Use userspace_pm_add_sf() to add a subflow, and pass initial
> ip address to userspace_pm_rm_sf() to remove the initial subflow.
>
> Signed-off-by: Geliang Tang <geliang.tang@suse.com>
> ---
> .../testing/selftests/net/mptcp/mptcp_join.sh | 26 +++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index ab6908b7b143..154978481409 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> @@ -3507,6 +3507,32 @@ userspace_tests()
> kill_events_pids
> wait $tests_pid
> fi
> +
> + # userspace pm remove initial subflow
> + if reset_with_events "userspace pm remove initial subflow" &&
> + continue_if mptcp_lib_has_file '/proc/sys/net/mptcp/pm_type'; then
> + set_userspace_pm $ns2
> + pm_nl_set_limits $ns1 0 1
> + speed=10 \
> + run_tests $ns1 $ns2 10.0.1.1 &
> + local tests_pid=$!
> + wait_mpj $ns2
> + userspace_pm_add_sf $ns2 10.0.3.2 20
> + chk_join_nr 1 1 1
> + chk_mptcp_info subflows 1 subflows 1
> + chk_subflows_total 2 2
> + userspace_pm_rm_sf $ns2 10.0.1.2
> + # we don't look at the counter linked to the RM_ADDR but
> + # to the one linked to the subflows that have been removed
> + chk_rm_nr 0 1
> + chk_rst_nr 0 0 invert
> + chk_mptcp_info subflows 1 subflows 1
> + # No subflow removed in ns1, one
> + # subflow has been removed in ns2
> + chk_subflows_total 2 1
We should really have "1 1" here: on both the client and the server
side, the initial subflow is being closed, so we should only have one
counter. Same comment on patch 7/7.
Maybe my suggestion from patch 3/7 will fix this issue.
Also, how are you checking this locally: with and without SS supporting
'subflows_total' counter?
Please note that the CI complained about these two tests (and the 2
others I mentioned before with 'subflows_total'). I suspect that you
also need to modify "chk_subflows_total()" and use 'state established'
filter for ss:
ss -N (...) -ti state established
No?
Cheers,
Matt
> + kill_events_pids
> + wait $tests_pid
> + fi
> }
>
> endpoint_tests()
--
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net
next prev parent reply other threads:[~2023-10-12 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 8:51 [PATCH mptcp-next v15 0/7] userspace pm remove id 0 subflow & address Geliang Tang
2023-10-12 8:51 ` [PATCH mptcp-next v15 1/7] selftests: mptcp: join: no RST when rm subflow/addr Geliang Tang
2023-10-12 14:36 ` Matthieu Baerts
2023-10-12 8:52 ` [PATCH mptcp-next v15 2/7] mptcp: add __mptcp_subflow_disconnect helper Geliang Tang
2023-10-12 8:52 ` [PATCH mptcp-next v15 3/7] Squash to "mptcp: add mptcpi_subflows_total counter" Geliang Tang
2023-10-12 14:36 ` Matthieu Baerts
2023-10-12 8:52 ` [PATCH mptcp-next v15 4/7] selftests: mptcp: userspace pm remove initial subflow Geliang Tang
2023-10-12 14:35 ` Matthieu Baerts [this message]
2023-10-12 8:52 ` [PATCH mptcp-next v15 5/7] mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-12 8:52 ` [PATCH mptcp-next v15 6/7] mptcp: userspace pm rename remove_err to out Geliang Tang
2023-10-12 8:52 ` [PATCH mptcp-next v15 7/7] selftests: mptcp: userspace pm send RM_ADDR for ID 0 Geliang Tang
2023-10-12 10:09 ` selftests: mptcp: userspace pm send RM_ADDR for ID 0: Tests Results 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=99e62e52-bbc1-4331-8f54-561cc207718b@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang.tang@suse.com \
--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