From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Zahka <daniel.zahka@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
willemb@google.com, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: drv-net: psp: fix test flakes from racy connection close
Date: Thu, 29 Jan 2026 03:50:22 +0000 [thread overview]
Message-ID: <176965862284.2339773.16368482662348009431.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260127-psp-flaky-test-v1-1-13403e390af3@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 27 Jan 2026 08:30:55 -0800 you wrote:
> There is a bug in assoc_sk_only_mismatch() and
> assoc_sk_only_mismatch_tx() that creates a race condition which
> triggers test flakes in later test cases e.g. data_send_bad_key().
>
> The problem is that the client uses the "conn clr" rpc to setup a data
> connection with psp_responder, but never uses a matching "data close"
> rpc. This creates a race condition where if the client can queue
> another data sock request, like in data_send_bad_key(), before the
> server can accept the old connection from the backlog we end up in a
> situation where we have two connections in the backlog: one for the
> closed connection we have received a FIN for, and one for the new PSP
> connection which is expecting to do key exchange.
>
> [...]
Here is the summary with links:
- [net-next] selftests: drv-net: psp: fix test flakes from racy connection close
https://git.kernel.org/netdev/net-next/c/70de46740b62
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-29 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 16:30 [PATCH net-next] selftests: drv-net: psp: fix test flakes from racy connection close Daniel Zahka
2026-01-29 3:50 ` patchwork-bot+netdevbpf [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=176965862284.2339773.16368482662348009431.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemb@google.com \
/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