From: Geliang Tang <geliang@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>,
Geliang Tang <tanggeliang@kylinos.cn>
Cc: mptcp@lists.linux.dev
Subject: Re: [RFC mptcp-next v10 00/14] MPTCP KTLS support
Date: Fri, 20 Mar 2026 15:45:52 +0800 [thread overview]
Message-ID: <d229f43010fd00178c87d2acd78bc7519d3c516d.camel@kernel.org> (raw)
In-Reply-To: <b7ce3e8b-dd6a-49c7-aede-23c846c6dfc4@kernel.org>
Hi Matt,
On Tue, 2026-03-17 at 14:15 +0100, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 17/03/2026 11:41, MPTCP CI wrote:
> > Hi Geliang,
> >
> > Thank you for your modifications, that's great!
> >
> > Our CI did some validations and here is its report:
> >
> > - KVM Validation: normal (except selftest_mptcp_join): Success! ✅
> > - KVM Validation: normal (only selftest_mptcp_join): Success! ✅
> > - KVM Validation: debug (except selftest_mptcp_join): Critical:
> > KMemLeak ❌
>
> It looks like the leak is linked to the new code. Is that right?
Yes, it's related to the changes to shutdown_reuse() in patch 12, and
it has been fixed in v11.
However, I noticed that v10 and v11 didn't trigger AI review. Any idea
why?
Thanks,
-Geliang
>
> No hurry if it is, it is just to make sure it is not linked to:
>
> https://github.com/multipath-tcp/mptcp_net-next/issues/583
>
> (if it is linked, then we have a reproducer, that might be helpful)
>
> Cheers,
> Matt
next prev parent reply other threads:[~2026-03-20 7:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 9:12 [RFC mptcp-next v10 00/14] MPTCP KTLS support Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 01/14] tls: introduce struct tls_prot_ops for protocol ops Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 02/14] tls: add tls_prot_ops pointer to tls_context Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 03/14] tls: add MPTCP SKB offset check in strp queue walk Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 04/14] mptcp: update mptcp_check_readable for TLS use Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 05/14] mptcp: avoid sleeping in read_sock path under softirq Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 06/14] mptcp: implement tls_mptcp_ops for MPTCP TLS Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 07/14] tls: disable device offload for MPTCP sockets Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 08/14] mptcp: update ULP getsockopt for TLS support Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 09/14] mptcp: enable ULP setsockopt " Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 10/14] selftests: mptcp: connect: use espintcp for ULP test Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 11/14] selftests: tls: add MPTCP variants for testing Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 12/14] selftests: tls: adjust timeouts and data for MPTCP Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 13/14] selftests: tls: add MPTCP test cases Geliang Tang
2026-03-17 9:12 ` [RFC mptcp-next v10 14/14] selftests: mptcp: add TLS tests to CI Geliang Tang
2026-03-17 10:41 ` [RFC mptcp-next v10 00/14] MPTCP KTLS support MPTCP CI
2026-03-17 13:15 ` Matthieu Baerts
2026-03-20 7:45 ` Geliang Tang [this message]
2026-03-20 8:07 ` Matthieu Baerts
2026-03-24 18:58 ` Matthieu Baerts
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=d229f43010fd00178c87d2acd78bc7519d3c516d.camel@kernel.org \
--to=geliang@kernel.org \
--cc=matttbe@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