From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754899AbeD3QcF (ORCPT ); Mon, 30 Apr 2018 12:32:05 -0400 Received: from mail-io0-f171.google.com ([209.85.223.171]:35108 "EHLO mail-io0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754631AbeD3QcE (ORCPT ); Mon, 30 Apr 2018 12:32:04 -0400 X-Google-Smtp-Source: AB8JxZo9LBSV+p09gIeRmMvr8fjuovUyfRODQkCFrYfo2ckynvjQSb8qLAFgkLmJd6iQWMdmXXvXCE+ATxk4C2mo1nE= MIME-Version: 1.0 References: In-Reply-To: From: Linus Torvalds Date: Mon, 30 Apr 2018 16:31:52 +0000 Message-ID: Subject: Re: Hashed pointer issues To: Kees Cook Cc: Anna-Maria Gleixner , Linux Kernel Mailing List , tcharding , Steven Rostedt 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 Mon, Apr 30, 2018 at 9:11 AM Kees Cook wrote: > I (or other folks?) had proposed this before, but, AIUI, Linus remains > opposed. Yeah, I hate this, because it will make people paper over their problems by just booting with that option. I think it should just be fixed. Is there really any reason why trace buffers have to be dumped so early that the entropy hasn't even taken yet? And if we really want a command line option, can we make that still hash the pointer, just force the entropy early. That way kernel developers that test that command line option are still testing the *hashing*, they just are missing the good entropy. Linus