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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1d2d919ae6848e2cf80b81ffe5f94fd31b8ea6ae.camel@gmail.com>
Date: Tue, 11 Feb 2025 12:15:25 -0800
From: Eduard Zingerman <eddyz87@...il.com>
To: Peilin Ye <yepeilin@...gle.com>
Cc: bpf@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 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>, Ilya Leoshkevich <iii@...ux.ibm.com>, Heiko Carstens
	 <hca@...ux.ibm.com>, Vasily Gorbik <gor@...ux.ibm.com>, Catalin Marinas	
 <catalin.marinas@....com>, Will Deacon <will@...nel.org>, Quentin Monnet	
 <qmo@...nel.org>, Mykola Lysenko <mykolal@...com>, Shuah Khan
 <shuah@...nel.org>,  Ihor Solodrai <ihor.solodrai@...ux.dev>, Yingchi Long
 <longyingchi24s@....ac.cn>, 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 v2 8/9] selftests/bpf: Add selftests for
 load-acquire and store-release instructions

On Tue, 2025-02-11 at 19:09 +0000, Peilin Ye wrote:

[...]

> > Nit: why is dummy_test() necessary?
> 
> It's just to make it clear when these tests are (effectively) skipped.
> Otherwise, e.g. -cpuv4 runner with LLVM-18 on x86-64 would give:
> 
>   #518     verifier_load_acquire:OK
> 
> With dummy_test(), we would see:
> 
> (FWIW, for v3 I'm planning to change __description() to the following,
> since new tests no longer depend on __BPF_FEATURE_LOAD_ACQ_STORE_REL.)
> 
>   #518/1   verifier_load_acquire/Clang version < 18, or JIT does not support load-acquire; use a dummy test:OK
>   #518     verifier_load_acquire:OK
> 
> Commit 147c8f4470ee ("selftests/bpf: Add unit tests for new
> sign-extension load insns") did similar thing in verifier_ldsx.c.

I see, thank you for explaining.
We do have a concept of skipped tests in the test-suite,
but it is implemented by calling test__skip() from the prog_tests/<smth>.c.
This would translate as something like below in prog_tests/verifier.c:

	void test_verifier_store_release(void) {
	#if defined(ENABLE_ATOMICS_TESTS) && defined(__TARGET_ARCH_arm64)
		RUN(verifier_store_release);
	#else
		test__skip()
	#endif
	}

The number of tests skipped is printed after tests execution.
Up to you if you'd like to change it like that or not.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ