From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v14 0/5] update userspace pm mptcp_info fields part 1
Date: Mon, 22 May 2023 21:11:57 +0800 [thread overview]
Message-ID: <cover.1684760588.git.geliang.tang@suse.com> (raw)
v14:
- drop mptcp_pm_remove_addrs helper in patch 1
- add two flags in patch 4, the address entry'll be removed from
userspace_pm_local_addr_list only when both flags are set, by doing this,
it's now independent of the order of the remove_subflows command and
the remove_addrs command.
v13:
- move the RM_ADDR command after the destruction of the subflow in
patch 2 and patch 5.
- drop mptcp_pm_remove_anno_list_by_saddr in mptcp_nl_cmd_sf_destroy in
patch 4.
- update userspace_pm.sh too in patch 5.
v12:
- address Matt's commits in v11.
v11:
- #1-#5 part 1, address Matt's comments in v10.
- #6-#9 part 2, update pm mptcp_info
- #10-#12 part 3, some cleanups.
v10:
- fix userspace_pm.sh errors reported by CI.
- fix the bug in mptcp_pm_remove_addrs in patch 1.
- drop msk->pm.subflow == 1 in mptcp_userspace_pm_delete_local_addr in
patch 3.
- exchange the order of "pm_nl_ctl rem" and "pm_nl_ctl dsf" in patch 2
and 6.
- update the commit logs.
v9:
- address Matt's commets in v8.
v8:
- address Matt's comments.
- split into two series, pt 2 will send later.
v7:
- fix userspace_pm.sh errors reported by CI.
- only remove addrs in mptcp_nl_cmd_remove().
v6:
- send a RM ADDR from userspace.
v5:
- fix a memleak error reported by CI.
- add more delay for userspace pm tests.
v4:
- add more patches
- add selftests
v3:
- update local_addr_used and add_addr_signaled
v2:
- hold pm locks
Geliang Tang (5):
mptcp: only send RM_ADDR in nl_cmd_remove
selftests: mptcp: update userspace pm addr tests
mptcp: export remove_anno_list_by_saddr
mptcp: add address into userspace pm list
selftests: mptcp: update userspace pm subflow tests
include/uapi/linux/mptcp.h | 2 +
net/mptcp/pm_netlink.c | 8 +-
net/mptcp/pm_userspace.c | 77 ++++++++++++++++++-
net/mptcp/protocol.h | 2 +
.../testing/selftests/net/mptcp/mptcp_join.sh | 11 ++-
.../selftests/net/mptcp/userspace_pm.sh | 3 +
6 files changed, 94 insertions(+), 9 deletions(-)
--
2.35.3
next reply other threads:[~2023-05-22 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 13:11 Geliang Tang [this message]
2023-05-22 13:11 ` [PATCH mptcp-next v14 1/5] mptcp: only send RM_ADDR in nl_cmd_remove Geliang Tang
2023-05-23 14:45 ` Matthieu Baerts
2023-05-22 13:11 ` [PATCH mptcp-next v14 2/5] selftests: mptcp: update userspace pm addr tests Geliang Tang
2023-05-22 13:12 ` [PATCH mptcp-next v14 3/5] mptcp: export remove_anno_list_by_saddr Geliang Tang
2023-05-22 13:12 ` [PATCH mptcp-next v14 4/5] mptcp: add address into userspace pm list Geliang Tang
2023-05-23 14:49 ` Matthieu Baerts
2023-05-22 13:12 ` [PATCH mptcp-next v14 5/5] selftests: mptcp: update userspace pm subflow tests Geliang Tang
2023-05-22 14:48 ` selftests: mptcp: update userspace pm subflow tests: Tests Results MPTCP CI
2023-05-23 14:49 ` [PATCH mptcp-next v14 5/5] selftests: mptcp: update userspace pm subflow tests Matthieu Baerts
2023-05-23 14:42 ` [PATCH mptcp-next v14 0/5] update userspace pm mptcp_info fields part 1 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.1684760588.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