[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGXu5jL00+BgNe7KJYXMBFNFg-qaNgkZyL2HAT5zzwRawFY6jg@mail.gmail.com>
Date: Thu, 7 Sep 2017 15:55:17 -0700
From: Kees Cook <keescook@...omium.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: David Howells <dhowells@...hat.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, Laura Abbott <labbott@...hat.com>,
"x86@...nel.org" <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 07/20] randstruct: Whitelist big_key path struct overloading
On Thu, Sep 7, 2017 at 12:20 AM, Christoph Hellwig <hch@...radead.org> wrote:
> On Mon, Jun 19, 2017 at 12:24:13PM -0700, Kees Cook wrote:
>> David, if you can Ack this, I'll carry it in my tree.
>
> This didn't seem to make it anywhere and we got the sad blacklist
> entry instead..
David, thoughts? It seems like a nice solution. If you don't object, I
could carry it in -next (and remove the randstruct whitelist entry)?
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
