From: Kees Cook <keescook@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Aleksa Sarai <cyphar@cyphar.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Dmitry Vyukov <dvyukov@google.com>,
Eric Biggers <ebiggers3@gmail.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Relocate execve() sanity checks
Date: Fri, 5 Jun 2020 18:45:37 -0700 [thread overview]
Message-ID: <202006051844.2EBA35A7@keescook> (raw)
In-Reply-To: <20200605174053.eea9557878d81024d2519e47@linux-foundation.org>
On Fri, Jun 05, 2020 at 05:40:53PM -0700, Andrew Morton wrote:
> On Fri, 5 Jun 2020 09:00:10 -0700 Kees Cook <keescook@chromium.org> wrote:
>
> > While looking at the code paths for the proposed O_MAYEXEC flag, I saw
> > some things that looked like they should be fixed up.
> >
> > exec: Change uselib(2) IS_SREG() failure to EACCES
> > This just regularizes the return code on uselib(2).
> >
> > exec: Move S_ISREG() check earlier
> > This moves the S_ISREG() check even earlier than it was already.
> >
> > exec: Move path_noexec() check earlier
> > This adds the path_noexec() check to the same place as the
> > S_ISREG() check.
>
> Thanks.
>
> These don't seem super-urgent and they aren't super-reviewed, so I
> suggest we hold them off until the next cycle?
Agreed; that's fine by me. It's mostly clean up and preparation for
performing future checking through the MAY_EXEC path.
And I'd love to get an Ack from Al or Aleksa, nudge nudge. :)
--
Kees Cook
prev parent reply other threads:[~2020-06-06 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 16:00 [PATCH v2 0/3] Relocate execve() sanity checks Kees Cook
2020-06-05 16:00 ` [PATCH v2 1/3] exec: Change uselib(2) IS_SREG() failure to EACCES Kees Cook
2020-06-05 16:00 ` [PATCH v2 2/3] exec: Move S_ISREG() check earlier Kees Cook
2020-08-13 14:13 ` Marc Zyngier
2020-08-13 17:13 ` Kees Cook
2020-06-05 16:00 ` [PATCH v2 3/3] exec: Move path_noexec() " Kees Cook
2020-06-06 0:40 ` [PATCH v2 0/3] Relocate execve() sanity checks Andrew Morton
2020-06-06 1:45 ` Kees Cook [this message]
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=202006051844.2EBA35A7@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=christian.brauner@ubuntu.com \
--cc=cyphar@cyphar.com \
--cc=dvyukov@google.com \
--cc=ebiggers3@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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