From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v7 0/7] userspace pm remove id 0 subflow & address
Date: Mon, 28 Aug 2023 12:35:22 +0800 [thread overview]
Message-ID: <cover.1693197152.git.geliang.tang@suse.com> (raw)
v7:
- move evts_get_info into mptcp_lib.sh, update userspace_pm.sh with
this helper too.
- drop the last two cleanup patches, they'll be sent in another series.
v6:
- add a new helper get_info_value, update chk_mptcp_info(),
verify_listener_events() and pedit_action_pkts() too.
- only patch 1, 2, 4 are changed, other patches are the same as v5.
v5:
- update userspace_pm_add_addr/sf helpers.
- add userspace_pm_rm_addr/sf helpers.
- remove id 0 subflow or address will send MP_RST, add chk_rst_nr for
them.
- add two selftests cleanups using for-loop.
v4:
- add evts_get_info and chk_subflows helpers.
- split the selftests patch into three.
v3:
- address Matt's comments in v2.
v2:
- fix CI errors.
This patchset addresses #379 and #391, add the abilities to remove id 0
subflow and address for userspace PM. And a selftest.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/379
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/391
Geliang Tang (7):
selftests: mptcp: add evts_get_info helper
selftests: mptcp: update userspace pm test helpers
selftests: mptcp: userspace pm remove id 0 subflow
mptcp: userspace pm allow creating id 0 subflow
selftests: mptcp: userspace pm create id 0 subflow
mptcp: userspace pm remove id 0 address
selftests: mptcp: userspace pm remove id 0 address
net/mptcp/pm_userspace.c | 40 +++-
.../testing/selftests/net/mptcp/mptcp_join.sh | 204 ++++++++++++------
.../testing/selftests/net/mptcp/mptcp_lib.sh | 20 ++
.../selftests/net/mptcp/userspace_pm.sh | 96 ++++-----
4 files changed, 235 insertions(+), 125 deletions(-)
--
2.35.3
next reply other threads:[~2023-08-28 4:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 4:35 Geliang Tang [this message]
2023-08-28 4:35 ` [PATCH mptcp-next v7 1/7] selftests: mptcp: add evts_get_info helper Geliang Tang
2023-08-28 4:35 ` [PATCH mptcp-next v7 2/7] selftests: mptcp: update userspace pm test helpers Geliang Tang
2023-08-28 4:35 ` [PATCH mptcp-next v7 3/7] selftests: mptcp: userspace pm remove id 0 subflow Geliang Tang
2023-08-28 4:35 ` [PATCH mptcp-next v7 4/7] mptcp: userspace pm allow creating " Geliang Tang
2023-08-28 4:35 ` [PATCH mptcp-next v7 5/7] selftests: mptcp: userspace pm create " Geliang Tang
2023-08-28 4:35 ` [PATCH mptcp-next v7 6/7] mptcp: userspace pm remove id 0 address Geliang Tang
2023-08-28 4:35 ` [PATCH mptcp-next v7 7/7] selftests: " Geliang Tang
2023-08-28 6:48 ` 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=cover.1693197152.git.geliang.tang@suse.com \
--to=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