From: Sam James <sam@gentoo.org>
To: Nirbhay Sharma <nirbhay.lkd@gmail.com>
Cc: Kees Cook <kees@kernel.org>, Shuah Khan <shuah@kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, llvm@lists.linux.dev, khalid@kernel.org,
david.hunter.linux@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org,
Jiri Olsa <olsajiri@gmail.com>
Subject: Re: [PATCH v2] selftests/seccomp: fix pointer type mismatch in UPROBE test
Date: Sun, 26 Oct 2025 10:44:50 +0000 [thread overview]
Message-ID: <87v7k2gcwt.fsf@gentoo.org> (raw)
In-Reply-To: <20251026091232.166638-2-nirbhay.lkd@gmail.com>
Nirbhay Sharma <nirbhay.lkd@gmail.com> writes:
> Fix compilation error in UPROBE_setup caused by pointer type mismatch
> in the ternary expression when compiled with -fcf-protection. The
> probed_uprobe function pointer has the __attribute__((nocf_check))
> attribute, which causes the conditional operator to fail when combined
> with the regular probed_uretprobe function pointer:
>
Just as a curiosity to share: I found a few tangential issues and
reported them as https://gcc.gnu.org/PR122427.
> seccomp_bpf.c:5175:74: error: pointer type mismatch in conditional
> expression [-Wincompatible-pointer-types]
>
> Cast both function pointers to 'const void *' to match the expected
> parameter type of get_uprobe_offset(), resolving the type mismatch
> while preserving the function selection logic.
>
> This error appears with compilers that enable Control Flow Integrity
> (CFI) protection via -fcf-protection, such as Clang 19.1.2 (default
> on Fedora).
>
Reviewed-by: Sam James <sam@gentoo.org>
> Signed-off-by: Nirbhay Sharma <nirbhay.lkd@gmail.com>
> ---
> tools/testing/selftests/seccomp/seccomp_bpf.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/seccomp/seccomp_bpf.c b/tools/testing/selftests/seccomp/seccomp_bpf.c
> index 874f17763536..e13ffe18ef95 100644
> --- a/tools/testing/selftests/seccomp/seccomp_bpf.c
> +++ b/tools/testing/selftests/seccomp/seccomp_bpf.c
> @@ -5172,7 +5172,8 @@ FIXTURE_SETUP(UPROBE)
> ASSERT_GE(bit, 0);
> }
>
> - offset = get_uprobe_offset(variant->uretprobe ? probed_uretprobe : probed_uprobe);
> + offset = get_uprobe_offset(variant->uretprobe ?
> + (const void *)probed_uretprobe : (const void *)probed_uprobe);
> ASSERT_GE(offset, 0);
>
> if (variant->uretprobe)
next prev parent reply other threads:[~2025-10-26 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 18:49 [PATCH] selftests/seccomp: fix pointer type mismatch in UPROBE test Nirbhay Sharma
2025-10-25 21:18 ` Jiri Olsa
2025-10-26 0:25 ` Sam James
2025-10-26 8:58 ` Nirbhay Sharma
2025-10-26 9:12 ` [PATCH v2] " Nirbhay Sharma
2025-10-26 10:44 ` Sam James [this message]
2025-10-27 8:14 ` Jiri Olsa
2025-11-25 11:20 ` Nirbhay Sharma
2025-12-03 15:59 ` Shuah Khan
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=87v7k2gcwt.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=bpf@vger.kernel.org \
--cc=david.hunter.linux@gmail.com \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=khalid@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@amacapital.net \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nirbhay.lkd@gmail.com \
--cc=olsajiri@gmail.com \
--cc=shuah@kernel.org \
--cc=wad@chromium.org \
/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.