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:20:42 +0800 [thread overview]
Message-ID: <f0621cfde5423d780c9eb9210e38f71c8493dcb5.camel@kernel.org> (raw)
In-Reply-To: <0a9f16f7-6991-8e13-7e2e-80f361579e33@gmail.com>
On Thu, 2026-04-02 at 08:17 +0000, MPTCP CI wrote:
> Hi Geliang,
>
> Thank you for your modifications, that's great!
>
> But sadly, our CI spotted some issues with it when trying to build
> it.
Oops.
protocol.c:(.text+0x2675f7): undefined reference to `lockdep_is_held'
I should use spin_is_locked(), not lockdep_is_held().
Will update this in the next version.
Thanks,
-Geliang
>
> You can find more details there:
>
>
> https://github.com/multipath-tcp/mptcp_net-next/actions/runs/23890722509
>
> Status: failure
> Initiator: Patchew Applier
> Commits:
> https://github.com/multipath-tcp/mptcp_net-next/commits/88f07fcab32d
> Patchwork:
> https://patchwork.kernel.org/project/mptcp/list/?series=1076267
>
> Feel free to reply to this email if you cannot access logs, if you
> need
> some support to fix the error, if this doesn't seem to be caused by
> your
> modifications or if the error is a false positive one.
>
> Cheers,
> MPTCP GH Action bot
> Bot operated by Matthieu Baerts (NGI0 Core)
next prev parent reply other threads:[~2026-04-02 10:20 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 [this message]
2026-04-02 9:21 ` MPTCP CI
2026-04-02 10:26 ` 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=f0621cfde5423d780c9eb9210e38f71c8493dcb5.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox