From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] execve updates for v6.8-rc1
Date: Mon, 8 Jan 2024 10:35:01 -0800 [thread overview]
Message-ID: <202401081028.0E908F9E0A@keescook> (raw)
Hi Linus,
Please pull these execve updates for v6.8-rc1. A fast-fail check has
been added to dramatically speed up execve-based PATH searches, and has
been in -next for the entire development window. A minor conflict with
netdev exists due to neighboring MAINTAINERS entries:
https://lore.kernel.org/linux-next/20231218161704.05c25766@canb.auug.org.au/
Thanks!
-Kees
The following changes since commit 21ca59b365c091d583f36ac753eaa8baf947be6f:
binfmt_misc: enable sandboxed mounts (2023-10-11 08:46:01 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/execve-v6.8-rc1
for you to fetch changes up to 0a8a952a75f2c5c140939c1616423e240677666c:
ELF, MAINTAINERS: specifically mention ELF (2023-12-06 14:55:31 -0800)
----------------------------------------------------------------
execve updates for v6.8-rc1
- Update MAINTAINERS entry to explicitly mention ELF (Alexey Dobriyan)
- Add a fail-fast check to speed up execve-based PATH searches (Josh
Triplett)
----------------------------------------------------------------
Alexey Dobriyan (1):
ELF, MAINTAINERS: specifically mention ELF
Josh Triplett (1):
fs/exec.c: Add fast path for ENOENT on PATH search before allocating mm
MAINTAINERS | 3 ++-
fs/exec.c | 13 +++++++++++++
2 files changed, 15 insertions(+), 1 deletion(-)
--
Kees Cook
next reply other threads:[~2024-01-08 18:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 18:35 Kees Cook [this message]
2024-01-09 0:19 ` [GIT PULL] execve updates for v6.8-rc1 Linus Torvalds
2024-01-09 0:30 ` Linus Torvalds
2024-01-09 0:46 ` Linus Torvalds
2024-01-09 1:48 ` Kees Cook
2024-01-09 1:53 ` Linus Torvalds
2024-01-09 3:28 ` Linus Torvalds
2024-01-09 18:57 ` Josh Triplett
2024-01-09 23:40 ` Linus Torvalds
2024-01-10 2:21 ` Josh Triplett
2024-01-10 3:54 ` Linus Torvalds
2024-01-11 9:47 ` Al Viro
2024-01-11 10:05 ` Al Viro
2024-01-11 17:42 ` Linus Torvalds
2024-01-20 22:18 ` Linus Torvalds
2024-01-21 8:05 ` Kees Cook
2024-01-11 17:37 ` Linus Torvalds
2024-01-10 19:24 ` Kees Cook
2024-01-10 20:12 ` 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=202401081028.0E908F9E0A@keescook \
--to=keescook@chromium.org \
--cc=adobriyan@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox