From: "Mickaël Salaün" <mic@digikod.net>
To: Sasha Levin <sashal@kernel.org>
Cc: "Kees Cook" <kees@kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, "Al Viro" <viro@zeniv.linux.org.uk>,
"Andy Lutomirski" <luto@amacapital.net>,
"Christian Brauner" <brauner@kernel.org>,
"Günther Noack" <gnoack@google.com>,
"Jeff Xu" <jeffxu@chromium.org>,
"Kees Cook" <keescook@chromium.org>,
"Mimi Zohar" <zohar@linux.ibm.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Paul Moore" <paul@paul-moore.com>,
"Roberto Sassu" <roberto.sassu@huawei.com>,
"Serge Hallyn" <serge@hallyn.com>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Stefan Berger" <stefanb@linux.ibm.com>,
"Nathan Chancellor" <nathan@kernel.org>
Subject: Re: [GIT PULL] AT_EXECVE_CHECK introduction for v6.14-rc1
Date: Mon, 20 Jan 2025 10:03:07 +0100 [thread overview]
Message-ID: <20250120.kab5eeng5Yai@digikod.net> (raw)
In-Reply-To: <Z42UFh7BThHtotDA@lappy>
On Sun, Jan 19, 2025 at 07:08:54PM -0500, Sasha Levin wrote:
> On Wed, Jan 15, 2025 at 04:18:07PM -0800, Kees Cook wrote:
> > Hi Linus,
> >
> > Please pull the AT_EXECVE_CHECK introduction for v6.14-rc1. I split
> > this series from the core execve tree since it's had a life of its own
> > as it has progressed from O_MAY_EXEC. :) This provides userspace with
> > a way to opt in to performing "execability" checks for things that are
> > executable but don't pass through execve(2) (e.g. scripts, dlopen libs,
> > etc). It's seen quite a bit of discussion and review, and has lived in
> > -next for the entire dev cycle. Included is documentation, samples, and
> > extensive selftests.
> >
> > Thanks!
> >
> > -Kees
> >
> > The following changes since commit fac04efc5c793dccbd07e2d59af9f90b7fc0dca4:
> >
> > Linux 6.13-rc2 (2024-12-08 14:03:39 -0800)
> >
> > are available in the Git repository at:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/AT_EXECVE_CHECK-v6.14-rc1
>
> Hey Kees,
>
> LKFT has caught a build error with one of the samples:
>
> /builds/linux/samples/check-exec/inc.c: In function 'interpret_stream':
> /builds/linux/samples/check-exec/inc.c:81:8: warning: implicit declaration of function 'execveat'; did you mean 'execve'? [-Wimplicit-function-declaration]
> err = execveat(fileno(script), "", script_argv, envp,
> ^~~~~~~~
> execve
>
> The full log is here: https://qa-reports.linaro.org/lkft/sashal-linus-next/build/v6.13-rc7-511-g109a8e0fa9d6/testrun/26809210/suite/build/test/gcc-8-allyesconfig/log
Hi Sasha,
Nathan caught this sample build issue last week too. The fix is here:
https://lore.kernel.org/r/20250115144753.311152-1-mic@digikod.net
next prev parent reply other threads:[~2025-01-20 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 0:18 [GIT PULL] AT_EXECVE_CHECK introduction for v6.14-rc1 Kees Cook
2025-01-20 0:08 ` Sasha Levin
2025-01-20 9:03 ` Mickaël Salaün [this message]
2025-01-20 21:39 ` Kees Cook
2025-01-23 4:49 ` pr-tracker-bot
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=20250120.kab5eeng5Yai@digikod.net \
--to=mic@digikod.net \
--cc=brauner@kernel.org \
--cc=gnoack@google.com \
--cc=jeffxu@chromium.org \
--cc=kees@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=nathan@kernel.org \
--cc=nfraprado@collabora.com \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=sashal@kernel.org \
--cc=serge@hallyn.com \
--cc=skhan@linuxfoundation.org \
--cc=stefanb@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.ibm.com \
/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.