public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Sabrina Dubroca <sd@queasysnail.net>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
	shuah@kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: tls: avoid flakiness in data_steal
Date: Thu, 8 Jan 2026 16:43:14 +0100	[thread overview]
Message-ID: <aV_Qkmfo6VPCN_gt@krikkit> (raw)
In-Reply-To: <20260106200205.1593915-1-kuba@kernel.org>

2026-01-06, 12:02:05 -0800, Jakub Kicinski wrote:
> We see the following failure a few times a week:
> 
>   #  RUN           global.data_steal ...
>   # tls.c:3280:data_steal:Expected recv(cfd, buf2, sizeof(buf2), MSG_DONTWAIT) (10000) == -1 (-1)
>   # data_steal: Test failed
>   #          FAIL  global.data_steal
>   not ok 8 global.data_steal
> 
> The 10000 bytes read suggests that the child process did a recv()
> of half of the data using the TLS ULP and we're now getting the
> remaining half. The intent of the test is to get the child to
> enter _TCP_ recvmsg handler, so it needs to enter the syscall before
> parent installed the TLS recvmsg with setsockopt(SOL_TLS).
> 
> Instead of the 10msec sleep send 1 byte of data and wait for the
> child to consume it.
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> CC: sd@queasysnail.net
> CC: shuah@kernel.org
> CC: linux-kselftest@vger.kernel.org
> ---
>  tools/testing/selftests/net/tls.c | 16 ++++++++++++----
>  1 file changed, 12 insertions(+), 4 deletions(-)

Reviewed-by: Sabrina Dubroca <sd@queasysnail.net>

-- 
Sabrina

  reply	other threads:[~2026-01-08 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 20:02 [PATCH net-next] selftests: tls: avoid flakiness in data_steal Jakub Kicinski
2026-01-08 15:43 ` Sabrina Dubroca [this message]
2026-01-10  1:40 ` patchwork-bot+netdevbpf

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=aV_Qkmfo6VPCN_gt@krikkit \
    --to=sd@queasysnail.net \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    /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