All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev, Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [RFC mptcp-next v12 00/15] MPTCP KTLS support
Date: Thu, 02 Apr 2026 18:26:33 +0800	[thread overview]
Message-ID: <8bb754486ad9151ab971fe25364f07894d8c5940.camel@kernel.org> (raw)
In-Reply-To: <fd0f8787-5395-4a72-451b-d348429e66a5@gmail.com>

On Thu, 2026-04-02 at 09:21 +0000, 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): Script error!
> ❓
> - KVM Validation: normal (only selftest_mptcp_join): Script error! ❓
> - KVM Validation: debug (except selftest_mptcp_join): Unstable: 3
> failed test(s): packetdrill_mp_capable packetdrill_sockopts
> selftest_mptcp_tls - Critical: KMemLeak ❌

It's strange.

Based-on: <cover.1775033340.git.yangang@kylinos.cn> tag didn't work,
this is "mptcp: fix stall because of data_ready" v5.

Without this set, the TLS tests failed. This resulted in a KMemLeak. If
this set is successfully applied, the tests will not fail, and there
will be no KMemLeak error.

Thanks,
-Geliang

> - KVM Validation: debug (only selftest_mptcp_join): Success! ✅
> - KVM Validation: btf-normal (only bpftest_all): Script error! ❓
> - KVM Validation: btf-debug (only bpftest_all): Success! ✅
> - Task:
> https://github.com/multipath-tcp/mptcp_net-next/actions/runs/23890722536
> 
> Initiator: Patchew Applier
> Commits:
> https://github.com/multipath-tcp/mptcp_net-next/commits/88f07fcab32d
> Patchwork:
> https://patchwork.kernel.org/project/mptcp/list/?series=1076267
> 
> 
> If there are some issues, you can reproduce them using the same
> environment as
> the one used by the CI thanks to a docker image, e.g.:
> 
>     $ cd [kernel source code]
>     $ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm
> -it \
>         --pull always mptcp/mptcp-upstream-virtme-docker:latest \
>         auto-normal
> 
> For more details:
> 
>     https://github.com/multipath-tcp/mptcp-upstream-virtme-docker
> 
> 
> Please note that despite all the efforts that have been already done
> to have a
> stable tests suite when executed on a public CI like here, it is
> possible some
> reported issues are not due to your modifications. Still, do not
> hesitate to
> help us improve that ;-)
> 
> Cheers,
> MPTCP GH Action bot
> Bot operated by Matthieu Baerts (NGI0 Core)

      reply	other threads:[~2026-04-02 10:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  7:47 [RFC mptcp-next v12 00/15] MPTCP KTLS support Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 01/15] tls: introduce struct tls_prot_ops Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 02/15] tls: add tls_prot_ops pointer to tls_context Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 03/15] tls: add skb offset check for mptcp Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 04/15] mptcp: update mptcp_check_readable Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 05/15] mptcp: implement tls_mptcp_ops Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 06/15] tls: disable device offload for mptcp sockets Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 07/15] mptcp: update ulp getsockopt for tls support Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 08/15] mptcp: enable ulp setsockopt " Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 09/15] selftests: mptcp: connect: use espintcp for ulp test Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 10/15] selftests: tls: add mptcp variant for testing Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 11/15] selftests: tls: increase pollin timeouts for mptcp Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 12/15] selftests: tls: increase nonblocking data size " Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 13/15] selftests: tls: wait close in shutdown_reuse " Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 14/15] selftests: tls: add mptcp test cases Geliang Tang
2026-04-02  7:47 ` [RFC mptcp-next v12 15/15] selftests: mptcp: cover mptcp tls tests Geliang Tang
2026-04-02  8:17 ` [RFC mptcp-next v12 00/15] MPTCP KTLS support MPTCP CI
2026-04-02 10:20   ` Geliang Tang
2026-04-02  9:21 ` MPTCP CI
2026-04-02 10:26   ` Geliang Tang [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=8bb754486ad9151ab971fe25364f07894d8c5940.camel@kernel.org \
    --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 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.