From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>,
David Gow <davidgow@google.com>, Kees Cook <kees@kernel.org>,
SeongJae Park <sj@kernel.org>
Subject: [GIT PULL] execve update for v6.11-rc1-fix1
Date: Tue, 23 Jul 2024 13:05:45 -0700 [thread overview]
Message-ID: <202407231304.04FE50257@keescook> (raw)
Hi Linus,
Please pull this execve fix for v6.11-rc1. This moves the exec and
binfmt_elf tests out of your way and into the tests/ subdirectory,
following the newly ratified KUnit naming conventions. :)
Thanks!
-Kees
The following changes since commit 21f93108306026b8066db31c24a097192c8c36c7:
exec: Avoid pathological argc, envc, and bprm->p values (2024-07-13 21:31:58 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/execve-v6.11-rc1-fix1
for you to fetch changes up to b6f5ee4d53019443fb99dd23bc08680b1244ccfa:
execve: Move KUnit tests to tests/ subdirectory (2024-07-22 18:25:47 -0700)
----------------------------------------------------------------
execve fix for v6.11-rc1
- Move KUnit tests to tests/ subdirectory
----------------------------------------------------------------
Kees Cook (1):
execve: Move KUnit tests to tests/ subdirectory
MAINTAINERS | 3 ++-
fs/binfmt_elf.c | 2 +-
fs/exec.c | 2 +-
fs/{binfmt_elf_test.c => tests/binfmt_elf_kunit.c} | 0
fs/{exec_test.c => tests/exec_kunit.c} | 0
5 files changed, 4 insertions(+), 3 deletions(-)
rename fs/{binfmt_elf_test.c => tests/binfmt_elf_kunit.c} (100%)
rename fs/{exec_test.c => tests/exec_kunit.c} (100%)
--
Kees Cook
next reply other threads:[~2024-07-23 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 20:05 Kees Cook [this message]
2024-07-24 1:21 ` [GIT PULL] execve update for v6.11-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=202407231304.04FE50257@keescook \
--to=kees@kernel.org \
--cc=brauner@kernel.org \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sj@kernel.org \
--cc=torvalds@linux-foundation.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.