BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	memxor@gmail.com, daniel@iogearbox.net, eddyz87@gmail.com,
	kuba@kernel.org
Subject: Re: [PATCH bpf-next v2] selftests/bpf: libarena: Avoid spurious spmc parallel selftest errors
Date: Tue, 09 Jun 2026 18:20:05 +0000	[thread overview]
Message-ID: <178102920590.2172433.205048003639089840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609063630.10245-1-emil@etsalapatis.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue,  9 Jun 2026 02:36:30 -0400 you wrote:
> The libarena parallel spmc selftest is nondeterministic by design.
> As a result it depends up to a point on the relative timing between the
> producer and consumer threads. This introduces the possibility for two
> kinds of spurious failures that this patch addresses.
> 
> 1) Spurious timeouts. The test proceeds in phases, and threads use a
>    common counter as a barrier to avoid proceeding to the next phase
>    until all threads are ready to do so. If a thread takes too long to
>    reach the barrier, the already waiting threads may time out.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] selftests/bpf: libarena: Avoid spurious spmc parallel selftest errors
    https://git.kernel.org/bpf/bpf-next/c/68f4e480b089

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-06-09 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09  6:36 [PATCH bpf-next v2] selftests/bpf: libarena: Avoid spurious spmc parallel selftest errors Emil Tsalapatis
2026-06-09 18:20 ` 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=178102920590.2172433.205048003639089840.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=kuba@kernel.org \
    --cc=memxor@gmail.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