From: Kees Cook <keescook@chromium.org>
To: Samuel Dionne-Riel <samuel@dionne-riel.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Graham Christensen <graham@grahamc.com>,
Oleg Nesterov <oleg@redhat.com>, Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Userspace regression in LTS and stable kernels
Date: Wed, 13 Feb 2019 16:54:07 -0800 [thread overview]
Message-ID: <CAGXu5jJoqnX54JnHZDVxO4NRCsT6sLH4+-TPk8GqCSVp0mFNLw@mail.gmail.com> (raw)
In-Reply-To: <CAN1fySXjLUYFw2JGQQ5xxqjX+6kygzqgUc6Oj-sbtq=ZjgfLTA@mail.gmail.com>
On Wed, Feb 13, 2019 at 4:41 PM Samuel Dionne-Riel
<samuel@dionne-riel.com> wrote:
> Before, the interpreter was still used (assuming it wasn't cut by the
> length), and the interpreter was free to re-read the shebang if
> desired.
Oh awesome. Yeah, so, nevermind about the WARN_ONCE().
So, to address the "wrong binary" problem, how about we ENOEXEC only
if no newline or spaces are found in the string?
--
Kees Cook
next prev parent reply other threads:[~2019-02-14 0:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 17:57 Userspace regression in LTS and stable kernels Samuel Dionne-Riel
2019-02-13 18:00 ` Samuel Dionne-Riel
2019-02-13 23:36 ` Richard Weinberger
2019-02-14 0:41 ` Samuel Dionne-Riel
2019-02-14 0:54 ` Kees Cook [this message]
2019-02-14 1:27 ` Samuel Dionne-Riel
2019-02-14 1:35 ` Kees Cook
2019-02-14 3:16 ` Samuel Dionne-Riel
2019-02-14 0:41 ` Kees Cook
2019-02-14 17:56 ` Linus Torvalds
2019-02-14 20:20 ` Andrew Morton
2019-02-15 7:00 ` Greg Kroah-Hartman
2019-02-15 7:13 ` Greg Kroah-Hartman
2019-02-15 9:10 ` Michal Hocko
2019-02-15 9:20 ` Greg Kroah-Hartman
2019-02-15 9:42 ` Michal Hocko
2019-02-15 15:19 ` Sasha Levin
2019-02-15 15:52 ` Michal Hocko
2019-02-15 16:18 ` Samuel Dionne-Riel
2019-02-15 18:02 ` Sasha Levin
2019-02-15 18:00 ` Sasha Levin
2019-02-18 12:56 ` Michal Hocko
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=CAGXu5jJoqnX54JnHZDVxO4NRCsT6sLH4+-TPk8GqCSVp0mFNLw@mail.gmail.com \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=graham@grahamc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=oleg@redhat.com \
--cc=richard.weinberger@gmail.com \
--cc=samuel@dionne-riel.com \
--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;
as well as URLs for NNTP newsgroup(s).