From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"Günther Noack" <gnoack3000@gmail.com>,
"Günther Noack" <gnoack@google.com>,
"Jeff Xu" <jeffxu@chromium.org>, "Kees Cook" <kees@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Mimi Zohar" <zohar@linux.ibm.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Paul Moore" <paul@paul-moore.com>,
"Roberto Sassu" <roberto.sassu@huawei.com>,
"Serge Hallyn" <serge@hallyn.com>,
"Stefan Berger" <stefanb@linux.ibm.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: [GIT PULL] AT_EXECVE_CHECK update for v6.14-rc1 (fix1)
Date: Fri, 31 Jan 2025 13:43:33 -0800 [thread overview]
Message-ID: <202501311342.42FE3BDF9@keescook> (raw)
Hi Linus,
Please pull this AT_EXECVE_CHECK fix for v6.14-rc1. Fixes the
AT_EXECVE_CHECK selftests which didn't run on old versions of glibc.
Thanks!
-Kees
The following changes since commit 95b3cdafd7cb74414070893445a9b731793f7b55:
ima: instantiate the bprm_creds_for_exec() hook (2024-12-18 17:00:29 -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-fix1
for you to fetch changes up to 38567b972a22706e9a1a52b2c4bc9ea4b5ed00ed:
selftests: Handle old glibc without execveat(2) (2025-01-27 11:37:18 -0800)
----------------------------------------------------------------
AT_EXECVE_CHECK update for v6.14-rc1 (fix1)
- selftests: Handle old glibc without execveat(2) (Mickaël Salaün)
----------------------------------------------------------------
Mickaël Salaün (1):
selftests: Handle old glibc without execveat(2)
samples/check-exec/inc.c | 11 +++++++++--
tools/testing/selftests/exec/check-exec.c | 11 +++++++++--
tools/testing/selftests/landlock/fs_test.c | 10 ++++++++--
3 files changed, 26 insertions(+), 6 deletions(-)
--
Kees Cook
next reply other threads:[~2025-01-31 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 21:43 Kees Cook [this message]
2025-02-01 1:20 ` [GIT PULL] AT_EXECVE_CHECK update for v6.14-rc1 (fix1) 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=202501311342.42FE3BDF9@keescook \
--to=kees@kernel.org \
--cc=gnoack3000@gmail.com \
--cc=gnoack@google.com \
--cc=jeffxu@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@digikod.net \
--cc=nathan@kernel.org \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=sfr@canb.auug.org.au \
--cc=stefanb@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox