From: Geliang Tang <geliang@kernel.org>
To: dust.li@linux.alibaba.com, mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>, Gang Yan <yangang@kylinos.cn>
Subject: Re: [RFC mptcp-next v9 09/10] selftests: mptcp: connect: set smc instead of tls
Date: Fri, 13 Mar 2026 16:04:38 +0800 [thread overview]
Message-ID: <5b5a0dfb286f60011750a83131bda08aeb779d29.camel@kernel.org> (raw)
In-Reply-To: <abOuAUaS1Rjutn-D@linux.alibaba.com>
Hi Dust,
On Fri, 2026-03-13 at 14:26 +0800, Dust Li wrote:
> On 2026-03-13 09:42:51, Geliang Tang wrote:
> > From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Hi Geliang,
>
> Thanks for the effort !
> But it's a pitty that SMC ULP support was removed in
> df31a6b0a305(Revert "net/smc: Introduce TCP ULP support") due to
> it violates some VFS assuptions :(
Thanks for the reminder. I will consider using another ULP instead.
-Geliang
>
> Best regards,
> Dust
>
> >
> > With KTLS being implemented, "tls" should no longer be used in
> > sock_test_tcpulp(), it breaks mptcp_connect.sh tests. Another ULP
> > name, "smc", is set instead in this patch.
> >
> > Cc: Dust Li <dust.li@linux.alibaba.com>
> > Co-developed-by: Gang Yan <yangang@kylinos.cn>
> > Signed-off-by: Gang Yan <yangang@kylinos.cn>
> > Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> > ---
> > tools/testing/selftests/net/mptcp/config | 1 +
> > tools/testing/selftests/net/mptcp/mptcp_connect.c | 2 +-
> > 2 files changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/net/mptcp/config
> > b/tools/testing/selftests/net/mptcp/config
> > index 59051ee2a986..18bd29ac5b24 100644
> > --- a/tools/testing/selftests/net/mptcp/config
> > +++ b/tools/testing/selftests/net/mptcp/config
> > @@ -34,3 +34,4 @@ CONFIG_NFT_SOCKET=m
> > CONFIG_NFT_TPROXY=m
> > CONFIG_SYN_COOKIES=y
> > CONFIG_VETH=y
> > +CONFIG_TLS=y
> > diff --git a/tools/testing/selftests/net/mptcp/mptcp_connect.c
> > b/tools/testing/selftests/net/mptcp/mptcp_connect.c
> > index cbe573c4ab3a..64c8a4bfe749 100644
> > --- a/tools/testing/selftests/net/mptcp/mptcp_connect.c
> > +++ b/tools/testing/selftests/net/mptcp/mptcp_connect.c
> > @@ -289,7 +289,7 @@ static void sock_test_tcpulp(int sock, int
> > proto, unsigned int line)
> > if (ret == 0)
> > X("setsockopt");
> > } else if (proto == IPPROTO_MPTCP) {
> > - ret = do_ulp_so(sock, "tls");
> > + ret = do_ulp_so(sock, "smc");
> > if (ret != -1)
> > X("setsockopt");
> > }
> > --
> > 2.53.0
next prev parent reply other threads:[~2026-03-13 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 1:42 [RFC mptcp-next v9 00/10] MPTCP KTLS support Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 01/10] tls: introduce struct tls_prot_ops Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 02/10] tls: add ops in tls_context Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 03/10] tls: add MPTCP SKB offset check in strp queue walk Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 04/10] mptcp: update mptcp_check_readable Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 05/10] mptcp: avoid deadlocks in read_sock path Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 06/10] mptcp: implement tls_mptcp_ops Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 07/10] mptcp: update ULP getsockopt Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 08/10] mptcp: enable TLS setsockopt Geliang Tang
2026-03-13 1:42 ` [RFC mptcp-next v9 09/10] selftests: mptcp: connect: set smc instead of tls Geliang Tang
2026-03-13 6:26 ` Dust Li
2026-03-13 8:04 ` Geliang Tang [this message]
2026-03-13 1:42 ` [RFC mptcp-next v9 10/10] selftests: mptcp: connect: add TLS tests Geliang Tang
2026-03-13 4:27 ` [RFC mptcp-next v9 00/10] MPTCP KTLS support MPTCP CI
2026-03-13 8:07 ` 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=5b5a0dfb286f60011750a83131bda08aeb779d29.camel@kernel.org \
--to=geliang@kernel.org \
--cc=dust.li@linux.alibaba.com \
--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