From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Kees Cook <kees@kernel.org>, Nir Lichtman <nir@lichtman.org>,
Tycho Andersen <tandersen@netflix.com>,
Vegard Nossum <vegard.nossum@oracle.com>
Subject: [GIT PULL] execve updates for v6.13-rc1 (take 2)
Date: Thu, 21 Nov 2024 06:53:17 -0800 [thread overview]
Message-ID: <202411210651.CD8B5A3B98@keescook> (raw)
Hi Linus,
Please pull these execve updates for v6.13-rc1 (take 2). I've dropped
the argv[0] vs "comm" setting patches. We'll work on the better solution
for the next merge window.
Thanks!
-Kees
The following changes since commit 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b:
Linux 6.12-rc2 (2024-10-06 15:32:27 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/execve-v6.13-rc1-take2
for you to fetch changes up to 45bf05a51842c4c274f94514195c2e99cc1c200c:
exec: remove legacy custom binfmt modules autoloading (2024-11-21 06:44:02 -0800)
----------------------------------------------------------------
execve updates for v6.13-rc1 (take2)
- binfmt_misc: Fix comment typos (Christophe JAILLET)
- exec: move empty argv[0] warning closer to actual logic (Nir Lichtman)
- exec: remove legacy custom binfmt modules autoloading (Nir Lichtman)
- coredump: Do not lock when copying "comm"
- MAINTAINERS: add auxvec.h and set myself as maintainer
----------------------------------------------------------------
Christophe JAILLET (1):
fs: binfmt: Fix a typo
Kees Cook (3):
coredump: Do not lock during 'comm' reporting
MAINTAINERS: exec: Add auxvec.h UAPI
MAINTAINERS: exec: Mark Kees as maintainer
Nir Lichtman (1):
exec: remove legacy custom binfmt modules autoloading
Tycho Andersen (1):
selftests/exec: add a test for execveat()'s comm
nir@lichtman.org (1):
exec: move warning of null argv to be next to the relevant code
MAINTAINERS | 3 +-
fs/binfmt_misc.c | 2 +-
fs/exec.c | 22 ++--------
include/linux/coredump.h | 4 +-
tools/testing/selftests/exec/execveat.c | 77 +++++++++++++++++++++++++++++++--
5 files changed, 83 insertions(+), 25 deletions(-)
--
Kees Cook
next reply other threads:[~2024-11-21 14:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 14:53 Kees Cook [this message]
2024-11-25 23:40 ` [GIT PULL] execve updates for v6.13-rc1 (take 2) Linus Torvalds
2024-11-26 5:09 ` Kees Cook
2024-11-26 20:11 ` Linus Torvalds
2024-11-26 20:12 ` Linus Torvalds
2024-11-28 0:53 ` Kees Cook
2024-11-28 1:59 ` Linus Torvalds
2024-11-28 2:05 ` Al Viro
2024-11-28 2:24 ` Linus Torvalds
2024-11-29 2:08 ` Kees Cook
2024-11-29 2:43 ` Linus Torvalds
2024-11-29 3:34 ` Al Viro
2024-11-29 4:23 ` Eric W. Biederman
2024-11-29 4:48 ` Al Viro
2024-11-29 17:00 ` Casey Schaufler
2024-11-29 19:33 ` Eric W. Biederman
2024-11-29 4:44 ` Linus Torvalds
2024-11-29 12:41 ` Eric W. Biederman
2024-11-29 21:42 ` Vegard Nossum
2024-11-29 22:54 ` Al Viro
2024-11-30 4:24 ` Linus Torvalds
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=202411210651.CD8B5A3B98@keescook \
--to=kees@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nir@lichtman.org \
--cc=tandersen@netflix.com \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.com \
--cc=viro@zeniv.linux.org.uk \
/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.