From: Kees Cook <kees@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] seccomp: Stub for !CONFIG_SECCOMP
Date: Wed, 8 Jan 2025 13:53:29 -0800 [thread overview]
Message-ID: <202501081352.6FF1687F67@keescook> (raw)
In-Reply-To: <20250107-seccomp-stub-2-v1-1-fd43bcee2560@linaro.org>
On Tue, Jan 07, 2025 at 09:46:48AM +0100, Linus Walleij wrote:
> When using !CONFIG_SECCOMP with CONFIG_GENERIC_ENTRY, the
> randconfig bots found the following snag:
>
> kernel/entry/common.c: In function 'syscall_trace_enter':
> >> kernel/entry/common.c:52:23: error: implicit declaration
> of function '__secure_computing' [-Wimplicit-function-declaration]
> 52 | ret = __secure_computing(NULL);
> | ^~~~~~~~~~~~~~~~~~
>
> Since generic entry calls __secure_computing() unconditionally,
> fix this by adding another static inline stub.
>
> Link: https://lore.kernel.org/oe-kbuild-all/202501061240.Fzk9qiFZ-lkp@intel.com/
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> include/linux/seccomp.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/include/linux/seccomp.h b/include/linux/seccomp.h
> index 341980599c71242d3bb95b544c954278efcc65b9..622a8d8899085b204c449e101de7fe59e26e15a2 100644
> --- a/include/linux/seccomp.h
> +++ b/include/linux/seccomp.h
> @@ -58,6 +58,10 @@ static inline int secure_computing(void) { return 0; }
> static inline int __secure_computing(const struct seccomp_data *sd) { return 0; }
^^^^
> #else
> static inline void secure_computing_strict(int this_syscall) { return; }
> +static inline int __secure_computing(const struct seccomp_data *sd)
> +{
> + return 0;
> +}
> #endif
Let's just move the existing __secure_computing() no-op out of the ifdef
there.
-Kees
>
> static inline long prctl_get_seccomp(void)
>
> ---
> base-commit: 40384c840ea1944d7c5a392e8975ed088ecf0b37
> change-id: 20250107-seccomp-stub-2-a2e8cbe1f949
>
> Best regards,
> --
> Linus Walleij <linus.walleij@linaro.org>
>
--
Kees Cook
prev parent reply other threads:[~2025-01-08 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 8:46 [PATCH] seccomp: Stub for !CONFIG_SECCOMP Linus Walleij
2025-01-08 21:53 ` Kees Cook [this message]
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=202501081352.6FF1687F67@keescook \
--to=kees@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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.