From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v13 0/5] update userspace pm mptcp_info fields pt 1
Date: Wed, 10 May 2023 12:20:07 +0800 [thread overview]
Message-ID: <cover.1683692137.git.geliang.tang@suse.com> (raw)
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 addr into userspace pm list
selftests: mptcp: update userspace pm subflow tests
net/mptcp/pm_netlink.c | 26 ++++++++--
net/mptcp/pm_userspace.c | 50 ++++++++++++++++++-
net/mptcp/protocol.h | 3 ++
.../testing/selftests/net/mptcp/mptcp_join.sh | 11 +++-
.../selftests/net/mptcp/userspace_pm.sh | 3 ++
5 files changed, 87 insertions(+), 6 deletions(-)
--
2.35.3
next reply other threads:[~2023-05-10 4:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 4:20 Geliang Tang [this message]
2023-05-10 4:20 ` [PATCH mptcp-next v13 1/5] mptcp: only send RM_ADDR in nl_cmd_remove Geliang Tang
2023-05-10 4:20 ` [PATCH mptcp-next v13 2/5] selftests: mptcp: update userspace pm addr tests Geliang Tang
2023-05-10 4:20 ` [PATCH mptcp-next v13 3/5] mptcp: export remove_anno_list_by_saddr Geliang Tang
2023-05-10 4:20 ` [PATCH mptcp-next v13 4/5] mptcp: add addr into userspace pm list Geliang Tang
2023-05-17 16:20 ` Matthieu Baerts
2023-05-10 4:20 ` [PATCH mptcp-next v13 5/5] selftests: mptcp: update userspace pm subflow tests Geliang Tang
2023-05-10 6:05 ` selftests: mptcp: update userspace pm subflow tests: Tests Results MPTCP CI
2023-05-17 16:14 ` [PATCH mptcp-next v13 0/5] update userspace pm mptcp_info fields pt 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.1683692137.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 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.