From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756135AbdIGWzU (ORCPT ); Thu, 7 Sep 2017 18:55:20 -0400 Received: from mail-io0-f175.google.com ([209.85.223.175]:33255 "EHLO mail-io0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755219AbdIGWzT (ORCPT ); Thu, 7 Sep 2017 18:55:19 -0400 X-Google-Smtp-Source: AOwi7QAcuc76CtCA/dMX6pZprFJBRMBcN0HRvc0bZNtpHaYa7nIP6IYmvpwwN/uYsudwW6h3e7TuuOmR42E0XjZTL8s= MIME-Version: 1.0 In-Reply-To: <20170907072029.GA15056@infradead.org> References: <1495829844-69341-1-git-send-email-keescook@chromium.org> <1495829844-69341-8-git-send-email-keescook@chromium.org> <20170528081249.GD22193@infradead.org> <20170907072029.GA15056@infradead.org> From: Kees Cook Date: Thu, 7 Sep 2017 15:55:17 -0700 X-Google-Sender-Auth: ZaO5mhYLB_un9-LDBhnWIZhictE Message-ID: Subject: Re: [PATCH v2 07/20] randstruct: Whitelist big_key path struct overloading To: Christoph Hellwig Cc: David Howells , "kernel-hardening@lists.openwall.com" , Laura Abbott , "x86@kernel.org" , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 7, 2017 at 12:20 AM, Christoph Hellwig 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