public inbox for mptcp@lists.linux.dev
 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 v7 0/9] MPTCP KTLS support
Date: Tue, 13 Jan 2026 14:13:26 +0800	[thread overview]
Message-ID: <cover.1768284047.git.tanggeliang@kylinos.cn> (raw)

From: Geliang Tang <tanggeliang@kylinos.cn>

v7:
 - Passing an MPTCP socket to tcp_sock_rate_check_app_limited() causes a
   crash. In v7, an MPTCP version of check_app_limited() is implemented,
   which calls tcp_sock_rate_check_app_limited() for each subflow.
 - Register tls_tcp_ops and tls_mptcp_ops in tls_register() rather than in
   tls_init().
 - Set ctx->ops in tls_init() instead of in do_tls_setsockopt_conf().
 - Keep tls_device.c unchanged. MPTCP TLS_HW mode has not been implemented
   yet, so EOPNOTSUPP is returned in this case.
 - Also add TCP TLS tests in mptcp_join.sh.

v6:
 - register each ops as Matt suggested.
 - drop sk_is_msk().
 - add tcp_sock_get_ulp/tcp_sock_set_ulp helpers.
 - set another ULP in sock_test_tcpulp as Matt suggested.
 - add tls tests using multiple subflows in mptcp_join.sh.
 - Link: https://patchwork.kernel.org/project/mptcp/cover/cover.1767518836.git.tanggeliang@kylinos.cn/

v5:
 - As suggested by Mat and Matt, this set introduces struct tls_prot_ops
   for TLS.
 - Includes Gang Yan's patches to add MPTCP support to the TLS selftests.
 - Link: https://patchwork.kernel.org/project/mptcp/cover/cover.1766372799.git.tanggeliang@kylinos.cn/

v4:
 - split "tls: add MPTCP protocol support" into smaller, more
   focused patches.
 - a new mptcp_inq helper has been implemented instead of directly
   using mptcp_inq_hint to fix the issue mentioned in [1].
 - add sk_is_msk helper.
 - the 'expect' parameter will no longer be added to sock_test_tcpulp.
   Instead, SOCK_TEST_TCPULP items causing the tests failure will be
   directly removed.
 - remove the "TCP KTLS" tests, keeping only the MPTCP-related ones.
 - Link: https://patchwork.kernel.org/project/mptcp/cover/cover.1765505775.git.tanggeliang@kylinos.cn/

[1]
https://patchwork.kernel.org/project/mptcp/patch/ce74452f4c095a1761ef493b767b4bd9f9c14359.1764333805.git.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.
 - Link: https://patchwork.kernel.org/project/mptcp/cover/cover.1763800601.git.tanggeliang@kylinos.cn/

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

Gang Yan (2):
  mptcp: allow overridden write_space to be invoked
  mptcp: update mptcp_check_readable

Geliang Tang (7):
  selftests: mptcp: add tcp tls tests
  tls: introduce struct tls_prot_ops
  tls: add ops in tls_context
  mptcp: implement tls_mptcp_ops
  mptcp: update ULP getsockopt
  mptcp: enable TLS setsockopt
  selftests: mptcp: add mptcp tls tests

 include/linux/tcp.h                           |   2 +
 include/net/mptcp.h                           |   2 +
 include/net/tcp.h                             |   1 +
 include/net/tls.h                             |  19 +++
 net/ipv4/tcp.c                                |  78 ++++++-----
 net/ipv4/tcp_rate.c                           |   9 +-
 net/mptcp/protocol.c                          | 125 ++++++++++++++++--
 net/mptcp/protocol.h                          |   2 +-
 net/mptcp/sockopt.c                           |  36 ++++-
 net/tls/tls_main.c                            |  93 ++++++++++++-
 net/tls/tls_strp.c                            |  28 ++--
 net/tls/tls_sw.c                              |   5 +-
 tools/testing/selftests/net/mptcp/config      |   1 +
 .../selftests/net/mptcp/mptcp_connect.c       |  53 +++++++-
 .../testing/selftests/net/mptcp/mptcp_join.sh |  45 ++++++-
 15 files changed, 435 insertions(+), 64 deletions(-)

-- 
2.51.0


             reply	other threads:[~2026-01-13  6:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  6:13 Geliang Tang [this message]
2026-01-13  6:13 ` [RFC mptcp-next v7 1/9] selftests: mptcp: add tcp tls tests Geliang Tang
2026-01-13  6:13 ` [RFC mptcp-next v7 2/9] tls: introduce struct tls_prot_ops Geliang Tang
2026-01-13  6:13 ` [RFC mptcp-next v7 3/9] tls: add ops in tls_context Geliang Tang
2026-01-13  6:13 ` [RFC mptcp-next v7 4/9] mptcp: allow overridden write_space to be invoked Geliang Tang
2026-01-13  6:13 ` [RFC mptcp-next v7 5/9] mptcp: update mptcp_check_readable Geliang Tang
2026-01-13  6:13 ` [RFC mptcp-next v7 6/9] mptcp: implement tls_mptcp_ops Geliang Tang
2026-01-13  6:13 ` [RFC mptcp-next v7 7/9] mptcp: update ULP getsockopt Geliang Tang
2026-01-13  6:13 ` [RFC mptcp-next v7 8/9] mptcp: enable TLS setsockopt Geliang Tang
2026-01-13  6:13 ` [RFC mptcp-next v7 9/9] selftests: mptcp: add mptcp tls tests Geliang Tang
2026-01-13  6:51 ` [RFC mptcp-next v7 0/9] MPTCP KTLS support MPTCP CI
2026-01-13  8:43 ` 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.1768284047.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