From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v2 0/3] implement psock_update_sk_prot
Date: Sun, 4 Jan 2026 13:29:41 +0800 [thread overview]
Message-ID: <cover.1767504329.git.tanggeliang@kylinos.cn> (raw)
From: Geliang Tang <tanggeliang@kylinos.cn>
v2:
- Include mptcp_bpf_update_proto within CONFIG_BPF_SYSCALL to fix the
compilation errors reported by the kernel test robot.
- Add checks for IS_ENABLED(CONFIG_MPTCP_IPV6).
Implement psock_update_sk_prot, for basic MPTCP BPF SOCKMAP support.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/521
Geliang Tang (3):
mptcp: implement psock_update_sk_prot
mptcp: allow overridden write_space to be invoked
selftests/bpf: Update sockmap tests for MPTCP
net/mptcp/protocol.c | 105 ++++++++++++++++++
net/mptcp/protocol.h | 2 +-
.../testing/selftests/bpf/prog_tests/mptcp.c | 4 +-
3 files changed, 108 insertions(+), 3 deletions(-)
--
2.51.0
next reply other threads:[~2026-01-04 5:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 5:29 Geliang Tang [this message]
2026-01-04 5:29 ` [PATCH mptcp-next v2 1/3] mptcp: implement psock_update_sk_prot Geliang Tang
2026-01-04 5:29 ` [PATCH mptcp-next v2 2/3] mptcp: allow overridden write_space to be invoked Geliang Tang
2026-02-03 6:54 ` Geliang Tang
2026-02-03 9:42 ` Matthieu Baerts
2026-02-03 10:31 ` Geliang Tang
2026-02-03 10:56 ` Matthieu Baerts
2026-02-03 11:13 ` Matthieu Baerts
2026-02-03 11:14 ` Matthieu Baerts
2026-02-04 11:56 ` Matthieu Baerts
2026-02-05 9:46 ` Geliang Tang
2026-01-04 5:29 ` [PATCH mptcp-next v2 3/3] selftests/bpf: Update sockmap tests for MPTCP Geliang Tang
2026-01-04 6:38 ` [PATCH mptcp-next v2 0/3] implement psock_update_sk_prot 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.1767504329.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