public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org
Subject: Re: [PATCH bpf-next v3] selftests/bpf: Fix arena_atomics failure due to llvm change
Date: Wed, 11 Sep 2024 17:20:29 +0000	[thread overview]
Message-ID: <172607522950.991126.876331589065223043.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240909223431.1666305-1-yonghong.song@linux.dev>

Hello:

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

On Mon,  9 Sep 2024 15:34:31 -0700 you wrote:
> llvm change [1] made a change such that __sync_fetch_and_{and,or,xor}()
> will generate atomic_fetch_*() insns even if the return value is not used.
> This is a deliberate choice to make sure barrier semantics are preserved
> from source code to asm insn.
> 
> But the change in [1] caused arena_atomics selftest failure.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3] selftests/bpf: Fix arena_atomics failure due to llvm change
    https://git.kernel.org/bpf/bpf-next/c/2897b1e2a2f4

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



      reply	other threads:[~2024-09-11 17:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 22:34 [PATCH bpf-next v3] selftests/bpf: Fix arena_atomics failure due to llvm change Yonghong Song
2024-09-11 17: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=172607522950.991126.876331589065223043.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=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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