[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jJ+UYXa3VxAghMwNfEsZ2g7PHJkdU7_SCCgOg9XEvy5Yw@mail.gmail.com>
Date: Mon, 31 Jul 2017 20:03:49 -0700
From: Kees Cook <keescook@...omium.org>
To: James Morris <jmorris@...ei.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
David Howells <dhowells@...hat.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
John Johansen <john.johansen@...onical.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
Paul Moore <paul@...l-moore.com>,
Stephen Smalley <sds@...ho.nsa.gov>,
Casey Schaufler <casey@...aufler-ca.com>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
James Morris <james.l.morris@...cle.com>,
Andy Lutomirski <luto@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 00/15] exec: Use sane stack rlimit under secureexec
On Mon, Jul 31, 2017 at 5:54 PM, James Morris <jmorris@...ei.org> wrote:
> On Mon, 31 Jul 2017, Kees Cook wrote:
>
>> Ugh, please ignore this v4. There's a typo that snuck in. I'll send a v5 soon...
>
> Aside from that, it's looking good. This touches a lot of stuff in
> security/ so it may make sense for it to go in via my tree.
Yeah, I'm open to whatever. It's not clear where it should go, but if
you want to take it and Linus doesn't want it "early", that works for
me. Linus, Andrew, thoughts?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists