From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: Re: [RFC mptcp-next 08/10] selftests: mptcp: connect: skip TLS in disconnect tests
Date: Tue, 18 Nov 2025 16:50:41 +0800 [thread overview]
Message-ID: <7f7380f782e729263e63c715cf5a0fecb34c501d.camel@kernel.org> (raw)
In-Reply-To: <0f303e07ce390055d0e68195530ae30ac33a2a5a.1763438045.git.tanggeliang@kylinos.cn>
On Tue, 2025-11-18 at 12:01 +0800, Geliang Tang wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Modify disconnect test scenarios to bypass TLS socket configuration
> since TLS setup can interfere with connection teardown validation.
> Add cfg_disconnect flag to control this behavior.
tls_disconnect() returning EOPNOTSUPP caused the MPTCP connect's
disconnect tests to fail:
static int tls_disconnect(struct sock *sk, int flags)
{
return -EOPNOTSUPP;
}
This patch can be dropped now that MPTCP support has been added to
tls_disconnect() like this:
static int tls_disconnect(struct sock *sk, int flags)
{
if (sk->sk_protocol == IPPROTO_MPTCP)
return mptcp_disconnect(sk, flags);
return -EOPNOTSUPP;
}
Thanks,
-Geliang
>
> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
> ---
> tools/testing/selftests/net/mptcp/mptcp_connect.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/net/mptcp/mptcp_connect.c
> b/tools/testing/selftests/net/mptcp/mptcp_connect.c
> index deafcff7a2c8..e43874610297 100644
> --- a/tools/testing/selftests/net/mptcp/mptcp_connect.c
> +++ b/tools/testing/selftests/net/mptcp/mptcp_connect.c
> @@ -79,6 +79,7 @@ static char *cfg_input;
> static int cfg_repeat = 1;
> static int cfg_truncate;
> static int cfg_rcv_trunc;
> +static int cfg_disconnect = 0;
>
> struct cfg_cmsg_types {
> unsigned int cmsg_enabled:1;
> @@ -434,7 +435,7 @@ static int sock_connect_mptcp(const char * const
> remoteaddr,
> }
>
> freeaddrinfo(addr);
> - if (sock != -1)
> + if (sock != -1 && cfg_disconnect == 0)
> SOCK_TEST_TCPULP(sock, proto, is_mptcp(sock));
> return sock;
> }
> @@ -1381,7 +1382,9 @@ int main_loop(void)
> again:
> check_getpeername_connect(fd);
>
> - SOCK_TEST_TCPULP(fd, cfg_sock_proto, -1);
> + /* Don't let TLS break disconnect tests */
> + if (cfg_disconnect == 0)
> + SOCK_TEST_TCPULP(fd, cfg_sock_proto, -1);
>
> if (cfg_rcvbuf)
> set_rcvbuf(fd, cfg_rcvbuf);
> @@ -1540,6 +1543,7 @@ static void parse_opts(int argc, char **argv)
> break;
> case 'I':
> cfg_repeat = atoi(optarg);
> + cfg_disconnect = 1;
> break;
> case 'l':
> listen_mode = true;
next prev parent reply other threads:[~2025-11-18 8:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 4:01 [RFC mptcp-next 00/10] MPTCP KTLS support Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 01/10] selftests: mptcp: sockopt: add protocol arguments Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 02/10] selftests: mptcp: sockopt: skip mptcp getsockopt for tcp tests Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 03/10] selftests: mptcp: sockopt: add TLS argument support Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 04/10] selftests: mptcp: sockopt: implement TCP TLS tests Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 05/10] tls: add MPTCP protocol support Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 06/10] mptcp: enable TLS socket options Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 07/10] selftests: mptcp: connect: enhance TCP ULP testing Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 08/10] selftests: mptcp: connect: skip TLS in disconnect tests Geliang Tang
2025-11-18 8:50 ` Geliang Tang [this message]
2025-11-18 4:01 ` [RFC mptcp-next 09/10] selftests: mptcp: connect: fix uninitialized variable warning Geliang Tang
2025-11-18 4:01 ` [RFC mptcp-next 10/10] selftests: mptcp: sockopt: add MPTCP TLS test cases Geliang Tang
2025-11-18 4:37 ` [RFC mptcp-next 00/10] MPTCP KTLS support MPTCP CI
2025-11-18 7:18 ` MPTCP CI
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=7f7380f782e729263e63c715cf5a0fecb34c501d.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.