lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6c7a14503338699fa99a4cf13f1e2b0abbfc9dfb.camel@gmail.com>
Date: Tue, 28 Jan 2025 18:17:29 -0800
From: Eduard Zingerman <eddyz87@...il.com>
To: Ihor Solodrai <ihor.solodrai@...ux.dev>, Peilin Ye
 <yepeilin@...gle.com>, 	bpf@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org
Cc: bpf@...f.org, Xu Kuohai <xukuohai@...weicloud.com>, David Vernet	
 <void@...ifault.com>, Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann	
 <daniel@...earbox.net>, Andrii Nakryiko <andrii@...nel.org>, Martin KaFai
 Lau	 <martin.lau@...ux.dev>, Song Liu <song@...nel.org>, Yonghong Song	
 <yonghong.song@...ux.dev>, John Fastabend <john.fastabend@...il.com>, KP
 Singh	 <kpsingh@...nel.org>, Stanislav Fomichev <sdf@...ichev.me>, Hao Luo	
 <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>, Jonathan Corbet	
 <corbet@....net>, "Paul E. McKenney" <paulmck@...nel.org>, Puranjay Mohan	
 <puranjay@...nel.org>, Catalin Marinas <catalin.marinas@....com>, Will
 Deacon	 <will@...nel.org>, Quentin Monnet <qmo@...nel.org>, Mykola Lysenko	
 <mykolal@...com>, Shuah Khan <shuah@...nel.org>, Josh Don
 <joshdon@...gle.com>,  Barret Rhoden <brho@...gle.com>, Neel Natu
 <neelnatu@...gle.com>, Benjamin Segall <bsegall@...gle.com>, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v1 7/8] selftests/bpf: Add selftests for
 load-acquire and store-release instructions

On Wed, 2025-01-29 at 02:07 +0000, Ihor Solodrai wrote:

[...]

> > This restriction would mean that tests are skipped on BPF CI, as it
> > 
> > currently runs using llvm 17 and 18. Instead, I suggest using some
> 
> Eduard, if this feature requires a particular version of LLVM, it's
> not difficult to add a configuration for it to BPF CI.
> 
> Whether we want to do it is an open question though. Issues may come
> up with other tests when newer LLVM is used.

These changes have not landed yet and would be in llvm main for some time.
The workaround is straightforward and I don't see a reason to add more jobs to CI.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ