From: Kees Cook <kees@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Shuah Khan <shuah@kernel.org>, Jakub Kicinski <kuba@kernel.org>,
Christian Brauner <brauner@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Eric Dumazet <edumazet@google.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
wine-devel@winehq.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 09/13] selftests/seccomp: Fix build warning
Date: Fri, 5 Dec 2025 14:21:34 -0800 [thread overview]
Message-ID: <202512051421.DCD77D0561@keescook> (raw)
In-Reply-To: <20251205171010.515236-10-linux@roeck-us.net>
On Fri, Dec 05, 2025 at 09:10:03AM -0800, Guenter Roeck wrote:
> Fix:
>
> seccomp_bpf.c: In function ‘UPROBE_setup’:
> seccomp_bpf.c:5175:74: warning: pointer type mismatch in conditional expression
>
> by type casting the argument to get_uprobe_offset().
>
> Fixes: 9ffc7a635c35a ("selftests/seccomp: validate uprobe syscall passes through seccomp")
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook
next prev parent reply other threads:[~2025-12-05 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 17:09 [PATCH v2 00/13] selftests: Fix build warnings and errors Guenter Roeck
2025-12-05 17:09 ` [PATCH v2 01/13] clone3: clone3_cap_checkpoint_restore: Fix build warnings Guenter Roeck
2025-12-05 17:09 ` [PATCH v2 02/13] selftests: ntsync: " Guenter Roeck
2025-12-08 19:27 ` Elizabeth Figura
2025-12-05 17:09 ` [PATCH v2 03/13] selftests/filesystems: fclog: Fix build warnings and errors Guenter Roeck
2025-12-05 17:09 ` [PATCH v2 04/13] selftests/filesystems: file_stressor: Fix build warning Guenter Roeck
2025-12-05 17:09 ` [PATCH v2 05/13] selftests/filesystems: anon_inode_test: " Guenter Roeck
2025-12-05 17:10 ` [PATCH v2 06/13] selftest: af_unix: Support compilers without flex-array-member-not-at-end support Guenter Roeck
2025-12-05 17:10 ` [PATCH v2 07/13] selftest/futex: Comment out test_futex_mpol Guenter Roeck
2025-12-05 17:10 ` [PATCH v2 08/13] selftests: net: netlink-dumps: Avoid uninitialized variable warning Guenter Roeck
2025-12-10 9:13 ` Jakub Kicinski
2025-12-10 19:09 ` Guenter Roeck
2025-12-05 17:10 ` [PATCH v2 09/13] selftests/seccomp: Fix build warning Guenter Roeck
2025-12-05 22:21 ` Kees Cook [this message]
2025-12-05 17:10 ` [PATCH v2 10/13] selftests: net: Fix build warnings Guenter Roeck
2025-12-05 17:10 ` [PATCH v2 11/13] selftests/fs/mount-notify: Fix build warning Guenter Roeck
2025-12-05 17:10 ` [PATCH v2 12/13] selftests/fs/mount-notify-ns: " Guenter Roeck
2025-12-05 17:31 ` Amir Goldstein
2025-12-05 18:26 ` Guenter Roeck
2025-12-05 17:10 ` [PATCH v2 13/13] selftests: net: tfo: " Guenter Roeck
2025-12-10 9:20 ` [PATCH v2 00/13] selftests: Fix build warnings and errors patchwork-bot+netdevbpf
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=202512051421.DCD77D0561@keescook \
--to=kees@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=edumazet@google.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=wine-devel@winehq.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.