From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v11 4/4] selftests: mptcp: userspace pm remove id 0 address
Date: Sun, 8 Oct 2023 13:25:52 +0200 [thread overview]
Message-ID: <01dfaf2a-e1a8-45ca-880d-be3a6e213703@kernel.org> (raw)
In-Reply-To: <3738a4c89c049ae3b2832206390a39471331865d.1696760702.git.geliang.tang@suse.com>
Hi Geliang,
On 08/10/2023 12:27, Geliang Tang wrote:
> This patch adds a selftest for userpsace PM to remove id 0 address.
> Use userspace_pm_add_addr() helper to add a id 10 address, then use
> userspace_pm_rm_addr() helper to remove id 0 address.
>
> Signed-off-by: Geliang Tang <geliang.tang@suse.com>
> ---
> .../testing/selftests/net/mptcp/mptcp_join.sh | 23 +++++++++++++++++++
> 1 file changed, 23 insertions(+)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_join.sh b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> index ce691aeca99e..30b9e367cefa 100755
> --- a/tools/testing/selftests/net/mptcp/mptcp_join.sh
> +++ b/tools/testing/selftests/net/mptcp/mptcp_join.sh
> @@ -3511,6 +3511,29 @@ userspace_tests()
> kill_events_pids
> wait $tests_pid
> fi
> +
> + # userspace pm remove id 0 address
> + if reset_with_events "userspace pm remove id 0 address" &&
Maybe clearer to say: "userspace pm send RM_ADDR for ID 0", no?
> + continue_if mptcp_lib_has_file '/proc/sys/net/mptcp/pm_type'; then
> + set_userspace_pm $ns1
> + pm_nl_set_limits $ns2 1 1
> + speed=10 \
> + run_tests $ns1 $ns2 10.0.1.1 &
> + local tests_pid=$!
> + wait_mpj $ns1
> + userspace_pm_add_addr $ns1 10.0.2.1 10
> + chk_join_nr 1 1 1
> + chk_add_nr 1 1
> + chk_mptcp_info subflows 1 subflows 1
> + chk_subflows_total 2 2
> + chk_mptcp_info add_addr_signal 1 add_addr_accepted 1
> + userspace_pm_rm_addr $ns1 0
> + chk_rm_nr 1 0 invert
> + chk_mptcp_info subflows 1 subflows 1
> + chk_subflows_total 2 2
(Is it really 2? I guess this is due to your patch 1/4 and we should
have 2 subflows in total here, no?)
After the server has sent a RM_ADDR for ID0, the client with the Netlink
PM will react by closing the subflow, no? If yes, please add a comment
explaining why the subflow has been removed after having sent a RM_ADDR
because it can be confusing.
Also, can you check that no RST has been sent?
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-08 11:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 10:27 [PATCH mptcp-next v11 0/4] userspace pm remove id 0 subflow & address Geliang Tang
2023-10-08 10:27 ` [PATCH mptcp-next v11 1/4] mptcp: set next subflow to msk->first Geliang Tang
2023-10-08 11:11 ` Matthieu Baerts
2023-10-08 12:33 ` Geliang Tang
2023-10-08 14:05 ` Matthieu Baerts
2023-10-10 6:04 ` Geliang Tang
2023-10-10 12:28 ` Matthieu Baerts
2023-10-08 10:27 ` [PATCH mptcp-next v11 2/4] selftests: mptcp: userspace pm remove initial subflow Geliang Tang
2023-10-08 11:13 ` Matthieu Baerts
2023-10-08 11:22 ` Matthieu Baerts
2023-10-08 10:27 ` [PATCH mptcp-next v11 3/4] mptcp: userspace pm remove id 0 address Geliang Tang
2023-10-08 11:19 ` Matthieu Baerts
2023-10-08 10:27 ` [PATCH mptcp-next v11 4/4] selftests: " Geliang Tang
2023-10-08 11:25 ` Matthieu Baerts [this message]
2023-10-08 12:20 ` selftests: mptcp: userspace pm remove id 0 address: 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=01dfaf2a-e1a8-45ca-880d-be3a6e213703@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 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.