From: Jiri Olsa <olsajiri@gmail.com>
To: bot+bpf-ci@kernel.org
Cc: andrii@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, eddyz87@gmail.com,
yonghong.song@linux.dev, clm@meta.com, ihor.solodrai@linux.dev
Subject: Re: [PATCHv2 bpf-next 4/5] selftests/bpf: Add test for checking correct nop of optimized usdt
Date: Tue, 10 Feb 2026 22:22:01 +0100 [thread overview]
Message-ID: <aYuheTlS8QtYbi4b@krava> (raw)
In-Reply-To: <189eab8445c1c9fa3b7e4c6dde23b4a30dc7f63ed2d3df62a1f8c889280f5927@mail.kernel.org>
On Tue, Feb 10, 2026 at 02:12:09PM +0000, bot+bpf-ci@kernel.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.
next prev parent reply other threads:[~2026-02-10 21:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:36 [PATCHv2 bpf-next 0/5] libbpf: Make optimized uprobes backward compatible Jiri Olsa
2026-02-10 13:36 ` [PATCHv2 bpf-next 1/5] libbpf: Add uprobe syscall feature detection Jiri Olsa
2026-02-10 13:36 ` [PATCHv2 bpf-next 2/5] libbpf: Add support to detect nop,nop5 instructions combo for usdt probe Jiri Olsa
2026-02-10 13:36 ` [PATCHv2 bpf-next 3/5] selftests/bpf: Emit nop,no5 instructions combo for x86_64 arch Jiri Olsa
2026-02-10 14:12 ` bot+bpf-ci
2026-02-10 13:36 ` [PATCHv2 bpf-next 4/5] selftests/bpf: Add test for checking correct nop of optimized usdt Jiri Olsa
2026-02-10 14:12 ` bot+bpf-ci
2026-02-10 21:22 ` Jiri Olsa [this message]
2026-02-10 13:36 ` [PATCHv2 bpf-next 5/5] selftests/bpf: Add usdt trigger bench Jiri Olsa
2026-02-10 14:12 ` bot+bpf-ci
2026-02-10 21:41 ` Jiri Olsa
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=aYuheTlS8QtYbi4b@krava \
--to=olsajiri@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.com \
--cc=yonghong.song@linux.dev \
/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.