From: Kees Cook <kees@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
Linus Walleij <linus.walleij@linaro.org>
Cc: Kees Cook <kees@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] seccomp: Stub for !HAVE_ARCH_SECCOMP_FILTER
Date: Tue, 22 Oct 2024 12:37:00 -0700 [thread overview]
Message-ID: <172962581580.4006205.14311870462068442574.b4-ty@kernel.org> (raw)
In-Reply-To: <20241022-seccomp-compile-error-v2-1-c9f08a4f8ebb@linaro.org>
On Tue, 22 Oct 2024 15:41:34 +0200, Linus Walleij wrote:
> If we have CONFIG_SECCOMP but not CONFIG_HAVE_ARCH_SECCOMP_FILTER
> we get a compilation error:
>
> ../kernel/entry/common.c: In function 'syscall_trace_enter':
> ../kernel/entry/common.c:55:23: error: implicit declaration of function '__secure_computing' [-Werror=implicit-function-declaration]
> 55 | ret = __secure_computing(NULL);
> | ^~~~~~~~~~~~~~~~~~
>
> [...]
Applied to for-next/seccomp, thanks!
[1/1] seccomp: Stub for !HAVE_ARCH_SECCOMP_FILTER
https://git.kernel.org/kees/c/8cf8dfceebda
Take care,
--
Kees Cook
prev parent reply other threads:[~2024-10-22 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 13:41 Linus Walleij
2024-10-22 19:37 ` 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=172962581580.4006205.14311870462068442574.b4-ty@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®