From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-net 0/4] fixes for userspace PM
Date: Thu, 1 Feb 2024 11:51:14 +0800 [thread overview]
Message-ID: <cover.1706759413.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
Fixes for "create an ID 0 subflow" and "map v4 address to v6".
Geliang Tang (4):
mptcp: add needs_id for userspace appending addr
mptcp: add needs_id for netlink appending addr
mptcp: map v4 address to v6 when destroying subflow
selftests: mptcp: rm subflow with v4/v4mapped addr
net/mptcp/pm_netlink.c | 24 +++++++++++++++----
net/mptcp/pm_userspace.c | 23 +++++++++++++-----
.../testing/selftests/net/mptcp/mptcp_join.sh | 11 ++++++---
3 files changed, 44 insertions(+), 14 deletions(-)
--
2.40.1
next reply other threads:[~2024-02-01 3:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 3:51 Geliang Tang [this message]
2024-02-01 3:51 ` [PATCH mptcp-net 1/4] mptcp: add needs_id for userspace appending addr Geliang Tang
2024-02-06 1:28 ` Mat Martineau
2024-02-01 3:51 ` [PATCH mptcp-net 2/4] mptcp: add needs_id for netlink " Geliang Tang
2024-02-01 5:35 ` Geliang Tang
2024-02-08 9:37 ` Matthieu Baerts
2024-02-06 1:28 ` Mat Martineau
2024-02-01 3:51 ` [PATCH mptcp-net 3/4] mptcp: map v4 address to v6 when destroying subflow Geliang Tang
2024-02-01 3:51 ` [PATCH mptcp-net 4/4] selftests: mptcp: rm subflow with v4/v4mapped addr Geliang Tang
2024-02-01 4:40 ` selftests: mptcp: rm subflow with v4/v4mapped addr: Tests Results MPTCP CI
2024-02-01 5:01 ` MPTCP CI
2024-02-06 1:40 ` [PATCH mptcp-net 4/4] selftests: mptcp: rm subflow with v4/v4mapped addr Mat Martineau
2024-02-06 5:47 ` Geliang Tang
2024-02-06 2:21 ` selftests: mptcp: rm subflow with v4/v4mapped addr: Tests Results MPTCP CI
2024-02-06 2:38 ` 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.1706759413.git.tanggeliang@kylinos.cn \
--to=geliang@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=tanggeliang@kylinos.cn \
/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