From: Shung-Hsi Yu <shung-hsi.yu@suse.com>
To: Emil Tsalapatis <emil@etsalapatis.com>,
Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: Eduard Zingerman <eddyz87@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, zhuyifei@google.com
Subject: Re: [PATCH bpf 0/2] bpf: fork state when comparing sign crossing ranges with zero
Date: Wed, 10 Jun 2026 19:07:38 +0800 [thread overview]
Message-ID: <ailAgHo123u37P-P@u94a> (raw)
In-Reply-To: <DIVKCTZ3SFXS.X30XCLLTRMQS@etsalapatis.com>
On Fri, May 29, 2026 at 07:53:08PM -0400, Emil Tsalapatis wrote:
> On Fri May 29, 2026 at 7:02 PM EDT, Ihor Solodrai wrote:
> > On 5/29/26 3:44 PM, Eduard Zingerman wrote:
> >> On Fri, 2026-05-29 at 01:13 -0700, Eduard Zingerman wrote:
[...]
> > Hi everyone,
> >
> > Apparently libarena_asan tests are currently skipped on BPF CI,
> > because they require clang 22 [1], which is not yet enabled there.
> >
> > I'll work on adding clang 22 to CI, but in the meanwhile please make
> > sure to test libarena locally with clang 22 if your changes are relevant.
> >
> > [1] https://lore.kernel.org/bpf/20260426190338.4615-6-emil@etsalapatis.com/
>
> We actually need Clang HEAD since that's the release with address
> space-specific support, is it possible to add it to the CI instead of
> 22? Alternatively we would have to wait for the Clang 23 RC in July.
Theorecially possible, the LLVM infrastructre at apt.llvm.org does
provide LLVM 23 snapshots (e.g. [1]), the problem awhile back was that
the infrasture had issues[2,3] so can't be used to install anything
newer than 21.
Just check again, and [2] seem to have been resolved[4]. While the
problem with installation script[3] thats left could probably be worked
around by adding the apt repositories directly.
1: https://apt.llvm.org/unstable/pool/main/l/llvm-toolchain-snapshot/
2: https://github.com/libbpf/ci/commit/af3742c19566425bf8fa3bd8425ea65917c55401
3: https://github.com/llvm/llvm-project/issues/180163
4: https://github.com/llvm/llvm-project/issues/179148#issuecomment-3963668474
next prev parent reply other threads:[~2026-06-10 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 8:13 [PATCH bpf 0/2] bpf: fork state when comparing sign crossing ranges with zero Eduard Zingerman
2026-05-29 8:13 ` [PATCH bpf 1/2] " Eduard Zingerman
2026-05-29 8:58 ` bot+bpf-ci
2026-05-29 18:22 ` Eduard Zingerman
2026-05-29 8:59 ` sashiko-bot
2026-05-29 18:23 ` Eduard Zingerman
2026-05-29 16:57 ` Emil Tsalapatis
2026-05-29 8:13 ` [PATCH bpf 2/2] selftests/bpf: test fork on zero comparison with wrapping ranges Eduard Zingerman
2026-05-29 17:03 ` Emil Tsalapatis
2026-05-29 22:44 ` [PATCH bpf 0/2] bpf: fork state when comparing sign crossing ranges with zero Eduard Zingerman
2026-05-29 23:02 ` Ihor Solodrai
2026-05-29 23:53 ` Emil Tsalapatis
2026-06-10 11:07 ` Shung-Hsi Yu [this message]
2026-05-30 0:23 ` Eduard Zingerman
2026-05-30 0:43 ` Emil Tsalapatis
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=ailAgHo123u37P-P@u94a \
--to=shung-hsi.yu@suse.com \
--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=ihor.solodrai@linux.dev \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yonghong.song@linux.dev \
--cc=zhuyifei@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.