From: Geliang Tang <geliang.tang@suse.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>
Subject: [PATCH mptcp-next v6 0/7] mptcp: update userspace pm mptcp_info fields
Date: Thu, 13 Apr 2023 17:12:35 +0800 [thread overview]
Message-ID: <cover.1681376983.git.geliang.tang@suse.com> (raw)
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 (7):
mptcp: pass addr to mptcp_pm_alloc_anno_list
mptcp: don't clear userspace pm addr id
mptcp: add addr into userspace pm list
mptcp: close remote subflow when destroying it
mptcp: increase userspace pm add_addr_signaled
mptcp: update userspace pm subflows
selftests: mptcp: check userspace mptcp_info
net/mptcp/pm.c | 21 +++++++++++++++----
net/mptcp/pm_netlink.c | 10 ++++-----
net/mptcp/pm_userspace.c | 16 ++++++++++++--
net/mptcp/protocol.h | 2 +-
.../testing/selftests/net/mptcp/mptcp_join.sh | 13 +++++++++++-
5 files changed, 49 insertions(+), 13 deletions(-)
--
2.35.3
next reply other threads:[~2023-04-13 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 9:12 Geliang Tang [this message]
2023-04-13 9:12 ` [PATCH mptcp-next v6 1/7] mptcp: pass addr to mptcp_pm_alloc_anno_list Geliang Tang
2023-04-13 9:12 ` [PATCH mptcp-next v6 2/7] mptcp: don't clear userspace pm addr id Geliang Tang
2023-04-13 9:12 ` [PATCH mptcp-next v6 3/7] mptcp: add addr into userspace pm list Geliang Tang
2023-04-13 9:12 ` [PATCH mptcp-next v6 4/7] mptcp: close remote subflow when destroying it Geliang Tang
2023-04-13 9:12 ` [PATCH mptcp-next v6 5/7] mptcp: increase userspace pm add_addr_signaled Geliang Tang
2023-04-13 9:12 ` [PATCH mptcp-next v6 6/7] mptcp: update userspace pm subflows Geliang Tang
2023-04-13 9:12 ` [PATCH mptcp-next v6 7/7] selftests: mptcp: check userspace mptcp_info Geliang Tang
2023-04-13 10:22 ` selftests: mptcp: check userspace mptcp_info: 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.1681376983.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