From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [PATCH mptcp-next 0/2] TLS disconnect support
Date: Wed, 14 Oct 2026 15:19:10 +0200 [thread overview]
Message-ID: <22c43778-503a-49a0-bc72-e9d9bc428360@kernel.org> (raw)
In-Reply-To: <cover.1791967771.git.tanggeliang@kylinos.cn>
Hi Geliang,
On 14/10/2026 10:59, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> To verify the correctness of MPTCP KTLS implementation, I added TLS test
> support to MPTCP selftests mptcp_connect.c. The test results showed that
> the disconnect test group failed with error code EOPNOTSUPP, so I added
> this series to support TLS disconnect.
I guess that's more a question for the KTLS maintainers, but my feeling
is that the disconnect is not supported on purpose because that's
probably not used in production, and source of many errors: see all the
bugs found around that for TCP and MPTCP (and others).
In fact, I just did a git blame, and found this: 5071a1e606b3 ("net:
tls: explicitly disallow disconnect").
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2026-10-14 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 8:59 [PATCH mptcp-next 0/2] TLS disconnect support Geliang Tang
2026-10-14 8:59 ` [PATCH mptcp-next 1/2] tls: implement tls_disconnect Geliang Tang
2026-10-14 9:42 ` sashiko-bot
2026-10-14 8:59 ` [PATCH mptcp-next 2/2] selftests: tls: update disconnect tests Geliang Tang
2026-10-14 10:06 ` [PATCH mptcp-next 0/2] TLS disconnect support MPTCP CI
2026-10-14 13:19 ` Matthieu Baerts [this message]
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=22c43778-503a-49a0-bc72-e9d9bc428360@kernel.org \
--to=matttbe@kernel.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.