MPTCP Linux Development
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [RFC mptcp-next v3 0/8] MPTCP KTLS support
Date: Sat, 22 Nov 2025 16:45:19 +0800	[thread overview]
Message-ID: <cover.1763800601.git.tanggeliang@kylinos.cn> (raw)

From: Geliang Tang <tanggeliang@kylinos.cn>

v3:
 - mptcp_read_sock() and mptcp_poll() are not exported, as mptcp_sockopt
   test does not use read_sock/poll interfaces. They will be exported when
   new tests are added in the future.
 - call mptcp_inq_hint in tls_device_rx_resync_new_rec(),
   tls_device_core_ctrl_rx_resync() and tls_read_flush_backlog() too.
 - update selftests. 

v2:
 - fix disconnect.
 - update selftests.

This series adds KTLS support for MPTCP. Since the ULP of msk is not being
used, ULP KTLS can be directly configured onto msk without affecting its
communication.

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/480

Depends on: implement mptcp read_sock, v13
Based-on: <cover.1761198660.git.geliang@kernel.org>

Geliang Tang (8):
  selftests: mptcp: sockopt: add protocol arguments
  selftests: mptcp: sockopt: enhance compatibility with TCP tests
  selftests: mptcp: sockopt: implement TCP TLS tests
  tls: add MPTCP protocol support
  mptcp: update ULP getsockopt
  mptcp: enable TLS setsockopt
  selftests: mptcp: connect: update sock_test_tcpulp
  selftests: mptcp: sockopt: cover MPTCP KTLS test cases

 include/net/mptcp.h                           |  33 +++++
 net/mptcp/protocol.c                          |  62 +++++++--
 net/mptcp/sockopt.c                           |  30 ++++-
 net/tls/tls_device.c                          |   8 +-
 net/tls/tls_main.c                            |   6 +-
 net/tls/tls_strp.c                            |  16 ++-
 net/tls/tls_sw.c                              |   4 +-
 tools/testing/selftests/net/mptcp/config      |   1 +
 .../selftests/net/mptcp/mptcp_connect.c       |  36 +++--
 .../selftests/net/mptcp/mptcp_sockopt.c       | 125 ++++++++++++++++--
 .../selftests/net/mptcp/mptcp_sockopt.sh      |  36 +++++
 11 files changed, 315 insertions(+), 42 deletions(-)

-- 
2.51.0


             reply	other threads:[~2025-11-22  8:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-22  8:45 Geliang Tang [this message]
2025-11-22  8:45 ` [RFC mptcp-next v3 1/8] selftests: mptcp: sockopt: add protocol arguments Geliang Tang
2025-11-22  8:45 ` [RFC mptcp-next v3 2/8] selftests: mptcp: sockopt: enhance compatibility with TCP tests Geliang Tang
2025-11-22  8:45 ` [RFC mptcp-next v3 3/8] selftests: mptcp: sockopt: implement TCP TLS tests Geliang Tang
2025-11-22  8:45 ` [RFC mptcp-next v3 4/8] tls: add MPTCP protocol support Geliang Tang
2025-11-22  8:45 ` [RFC mptcp-next v3 5/8] mptcp: update ULP getsockopt Geliang Tang
2025-11-22  8:45 ` [RFC mptcp-next v3 6/8] mptcp: enable TLS setsockopt Geliang Tang
2025-11-22  8:45 ` [RFC mptcp-next v3 7/8] selftests: mptcp: connect: update sock_test_tcpulp Geliang Tang
2025-11-22  8:45 ` [RFC mptcp-next v3 8/8] selftests: mptcp: sockopt: cover MPTCP KTLS test cases Geliang Tang
2025-11-22 11:15 ` [RFC mptcp-next v3 0/8] MPTCP KTLS support 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.1763800601.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