public inbox for mptcp@lists.linux.dev
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>, Gang Yan <yangang@kylinos.cn>
Subject: Re: [RFC mptcp-next v5 6/8] selftests: mptcp: sockopt: implement MPTCP KTLS tests
Date: Tue, 23 Dec 2025 17:38:42 +0100	[thread overview]
Message-ID: <d97b77d8-c97c-46be-b64e-590b93055f79@kernel.org> (raw)
In-Reply-To: <fb08cb01f9dfa6ae1a61680390e074330e9b252c.1766372799.git.tanggeliang@kylinos.cn>

Hi Geliang,

On 22/12/2025 04:15, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
> 
> This patch adds Kernel TLS (KTLS) testing infrastructure to MPTCP sockopt
> selftest, introducing a new '-c' option to enable TLS tests. It includes
> a helper for configuring TLS socket options and implements MPTCP-specific
> KTLS test cases for both IPv4 and IPv6, along with the necessary header
> includes and config updates.
> 
> TLS_OVERHEAD_SIZE macro is defined to account for the overhead in sent
> and received data length.

When quickly looking at the code and the commit message, it is not clear
what this does: does it only set the TLS socket options, and that's it?
If yes, that's not enough, and it might give confusing results if the
new feature is not "properly" tested.

I think a "proper" test would involve transferring data with multiple
subflows (with data going through the different subflows and correctly
processed). That's more complex to put in place, but this looks required.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  reply	other threads:[~2025-12-23 16:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22  3:15 [RFC mptcp-next v5 0/8] MPTCP KTLS support Geliang Tang
2025-12-22  3:15 ` [RFC mptcp-next v5 1/8] tls: introduce struct tls_prot_ops Geliang Tang
2025-12-23 16:36   ` Matthieu Baerts
2025-12-22  3:15 ` [RFC mptcp-next v5 2/8] mptcp: implement tls_mptcp_ops Geliang Tang
2025-12-22  3:15 ` [RFC mptcp-next v5 3/8] mptcp: update ULP getsockopt Geliang Tang
2025-12-23 16:36   ` Matthieu Baerts
2025-12-22  3:15 ` [RFC mptcp-next v5 4/8] mptcp: enable TLS setsockopt Geliang Tang
2025-12-23 16:37   ` Matthieu Baerts
2025-12-22  3:15 ` [RFC mptcp-next v5 5/8] selftests: mptcp: connect: update sock_test_tcpulp Geliang Tang
2025-12-23 16:38   ` Matthieu Baerts
2025-12-22  3:15 ` [RFC mptcp-next v5 6/8] selftests: mptcp: sockopt: implement MPTCP KTLS tests Geliang Tang
2025-12-23 16:38   ` Matthieu Baerts [this message]
2025-12-22  3:15 ` [RFC mptcp-next v5 7/8] mptcp: fix the mptcp_check_readable Geliang Tang
2025-12-23 16:39   ` Matthieu Baerts
2025-12-22  3:15 ` [RFC mptcp-next v5 8/8] selftests: tls: add a '--mptcp' test mode Geliang Tang
2025-12-23 16:39   ` Matthieu Baerts
2025-12-23 16:35 ` [RFC mptcp-next v5 0/8] MPTCP KTLS support Matthieu Baerts
2026-01-04  9:52   ` Geliang Tang

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=d97b77d8-c97c-46be-b64e-590b93055f79@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    --cc=yangang@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