From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: Josh Triplett <josh@joshtriplett.org>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: [GIT PULL] execve updates for v6.8-rc1
Date: Sun, 21 Jan 2024 00:05:34 -0800 [thread overview]
Message-ID: <F3CF53C5-6423-4DA3-83CA-86B8B8C3862C@kernel.org> (raw)
In-Reply-To: <CAHk-=whw936qzDLBQdUz-He5WK_0fRSWwKAjtbVsMGfX70Nf_Q@mail.gmail.com>
On January 20, 2024 2:18:36 PM PST, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>End result: I committed my "move do_open_execat() to the beginning of
>execve()" patch, since it's clearly an improvement on the existing
>behavior, and that whole "struct file allocations are unnecessarily
>expensive" issue is a separate thing.
Thanks! I'll add the other bits of refactoring I did in my version of the clean-up (I created do_close_execat() for the repeated "allow_write_access(file); fput(file);" calls, along with some comments):
https://lore.kernel.org/lkml/202209161637.9EDAF6B18@keescook/
I like your removal of the "out" label! :)
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-01-21 8:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 18:35 Kees Cook
2024-01-09 0:19 ` 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 [this message]
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=F3CF53C5-6423-4DA3-83CA-86B8B8C3862C@kernel.org \
--to=kees@kernel.org \
--cc=adobriyan@gmail.com \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®