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: [PATCH mptcp-next v6 0/7] mptcp: TCP_MD5SIG support
Date: Wed,  5 Nov 2025 17:29:23 +0800	[thread overview]
Message-ID: <cover.1762334694.git.tanggeliang@kylinos.cn> (raw)

From: Geliang Tang <tanggeliang@kylinos.cn>

v6:
 - update selftests.
 - move "tcp: md5: remove redundant l3flag variable" into this set.

v5:
 - new selftests for MD5.
Link: https://patchwork.kernel.org/project/mptcp/cover/cover.1754837808.git.tanggeliang@kylinos.cn/

v4:
 - drop CONFIG_TCP_MD5SIG check.
 - drop sk_state check.
 - use WARN_ON_ONCE for __mptcp_try_fallback().

v3:
 - limit the use of these options for listened and closed state.
 - check the return value of __mptcp_try_fallback().

v2:
 - trigger fallback to TCP.
 - check CONFIG_TCP_MD5SIG.
 - update MD5 comment.
 - drop selftests, packetdrill tests will be added later.

This series introduces support for TCP_MD5SIG socket options in MPTCP along
with code improvements:

Patch 1: Refactors TCP_MAXSEG getsockopt handling to improve code
consistency
Patch 2: Adds setsockopt support for TCP_MD5SIG/TCP_MD5SIG_EXT (first
subflow only)

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

Geliang Tang (7):
  tcp: md5: remove redundant l3flag variable
  mptcp: handle TCP_MAXSEG getsockopt in common case
  mptcp: setsockopt support for TCP_MD5SIG
  selftests: mptcp: sockopt: add md5 argument
  selftests: mptcp: sockopt: implement TCP_MD5SIG support
  selftests: mptcp: sockopt: skip getsockopt for MD5 tests
  selftests: mptcp: sockopt: add TCP_MD5SIG test cases

 net/ipv4/tcp_ipv4.c                           |  7 +-
 net/ipv6/tcp_ipv6.c                           |  9 +-
 net/mptcp/sockopt.c                           | 18 ++--
 net/mptcp/subflow.c                           |  3 +
 tools/testing/selftests/net/mptcp/config      |  3 +
 .../selftests/net/mptcp/mptcp_sockopt.c       | 86 ++++++++++++++++---
 .../selftests/net/mptcp/mptcp_sockopt.sh      | 51 +++++++++++
 7 files changed, 147 insertions(+), 30 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-11-05  9:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05  9:29 Geliang Tang [this message]
2025-11-05  9:29 ` [PATCH mptcp-next v6 1/7] tcp: md5: remove redundant l3flag variable Geliang Tang
2025-11-05  9:29 ` [PATCH mptcp-next v6 2/7] mptcp: handle TCP_MAXSEG getsockopt in common case Geliang Tang
2025-11-05  9:29 ` [PATCH mptcp-next v6 3/7] mptcp: setsockopt support for TCP_MD5SIG Geliang Tang
2025-11-05  9:29 ` [PATCH mptcp-next v6 4/7] selftests: mptcp: sockopt: add md5 argument Geliang Tang
2025-11-05  9:29 ` [PATCH mptcp-next v6 5/7] selftests: mptcp: sockopt: implement TCP_MD5SIG support Geliang Tang
2025-11-05  9:29 ` [PATCH mptcp-next v6 6/7] selftests: mptcp: sockopt: skip getsockopt for MD5 tests Geliang Tang
2025-11-05  9:29 ` [PATCH mptcp-next v6 7/7] selftests: mptcp: sockopt: add TCP_MD5SIG test cases Geliang Tang
2025-11-05 11:37 ` [PATCH mptcp-next v6 0/7] mptcp: TCP_MD5SIG 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.1762334694.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