From: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
To: "George Guo" <dongtai.guo@linux.dev>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>
Cc: "Eduard Zingerman" <eddyz87@gmail.com>,
"Emil Tsalapatis" <emil@etsalapatis.com>,
"Mykola Lysenko" <mykolal@fb.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Kumar Kartikeya Dwivedi" <memxor@gmail.com>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Tiezhu Yang" <yangtiezhu@loongson.cn>,
"George Guo" <guodongtai@kylinos.cn>, <bpf@vger.kernel.org>,
<loongarch@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf] selftests/bpf: Skip libarena when the BPF backend lacks 32-bit arena cmpxchg
Date: Tue, 30 Jun 2026 11:06:30 -0700 [thread overview]
Message-ID: <DJML0UYPUL9U.P5NHVG4E32LW@gmail.com> (raw)
In-Reply-To: <20260630025809.74043-1-dongtai.guo@linux.dev>
On Mon Jun 29, 2026 at 7:58 PM PDT, George Guo wrote:
> From: George Guo <guodongtai@kylinos.cn>
>
> The arena qspinlock pulled in by libarena (bpf_arena_spin_lock.h) performs
> a 32-bit atomic compare-and-exchange on an arena (address space 1) pointer
> via atomic_try_cmpxchg_acquire() on the 32-bit atomic_t lock word. Not
> every LLVM BPF backend can select that operation; releases such as clang 19
> abort instruction selection with:
Sorry, you have to upgrade your test environment.
We won't be disabling tests because people still have old clang or old gcc
or other older tools in their setups.
pw-bot: cr
prev parent reply other threads:[~2026-06-30 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 2:58 [PATCH bpf] selftests/bpf: Skip libarena when the BPF backend lacks 32-bit arena cmpxchg George Guo
2026-06-30 3:16 ` sashiko-bot
2026-06-30 18:06 ` Alexei Starovoitov [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=DJML0UYPUL9U.P5NHVG4E32LW@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenhuacai@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dongtai.guo@linux.dev \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=guodongtai@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mykolal@fb.com \
--cc=yangtiezhu@loongson.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox