linux-kernel - Re: [PATCHv2 bpf-next 4/5] selftests/bpf: Add test for checking correct nop of optimized usdt

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: <aYuheTlS8QtYbi4b@krava>
Date: Tue, 10 Feb 2026 22:22:01 +0100
From: Jiri Olsa <olsajiri@...il.com>
To: bot+bpf-ci@...nel.org
Cc: andrii@...nel.org, bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
	songliubraving@...com, yhs@...com, john.fastabend@...il.com,
	ast@...nel.org, daniel@...earbox.net, martin.lau@...nel.org,
	eddyz87@...il.com, yonghong.song@...ux.dev, clm@...a.com,
	ihor.solodrai@...ux.dev
Subject: Re: [PATCHv2 bpf-next 4/5] selftests/bpf: Add test for checking
 correct nop of optimized usdt

On Tue, Feb 10, 2026 at 02:12:09PM +0000, bot+bpf-ci@...nel.org wrote:
> > diff --git a/tools/testing/selftests/bpf/prog_tests/usdt.c b/tools/testing/selftests/bpf/prog_tests/usdt.c
> > --- a/tools/testing/selftests/bpf/prog_tests/usdt.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/usdt.c
> 
> [ ... ]
> 
> > +#ifdef __x86_64
>           ^^^^^^^^
> Should this be __x86_64__ (with trailing underscores) to match the standard
> GCC predefined macro? The call site in test_usdt() uses __x86_64__:
> 
> > @@ -516,6 +599,8 @@ void test_usdt(void)
> > #ifdef __x86_64__
> > 	if (test__start_subtest("basic_optimized"))
> > 		subtest_basic_usdt(true);
> > +	if (test__start_subtest("optimized_attach"))
> > +		subtest_optimized_attach();
> > #endif
> 
> Without the trailing underscores, the function definition will not be
> compiled on x86_64 while the call will be, leading to a linker error.

it actually compiles, interestingly enough __x86_64 is allowed as well,
but it's a typo.. will fix, thnx

jirka

> 
> 
> ---
> AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
> See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
> 
> CI run summary: https://github.com/kernel-patches/bpf/actions/runs/21867569087
> 
> AI-authorship-score: low
> AI-authorship-explanation: The commit follows standard kernel selftest patterns with a natural coding style and contains a typo characteristic of human error rather than AI generation.
> issues-found: 1
> issue-severity-score: medium
> issue-severity-explanation: The mismatched preprocessor macro will cause a linker error on x86_64 builds, preventing the test from compiling.