From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752392AbeAZQn1 (ORCPT ); Fri, 26 Jan 2018 11:43:27 -0500 Received: from www.llwyncelyn.cymru ([82.70.14.225]:46084 "EHLO fuzix.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751836AbeAZQn0 (ORCPT ); Fri, 26 Jan 2018 11:43:26 -0500 Date: Fri, 26 Jan 2018 16:43:10 +0000 From: Alan Cox To: "Jason A. Donenfeld" Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, kernel-hardening@lists.openwall.com Subject: Re: [PATCH v2] cpu: do not leak vulnerabilities to unprivileged users Message-ID: <20180126164310.13a29ad2@alans-desktop> In-Reply-To: <20180126123158.9575-1-Jason@zx2c4.com> References: <20180126123158.9575-1-Jason@zx2c4.com> Organization: Intel Corporation X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 26 Jan 2018 13:31:58 +0100 "Jason A. Donenfeld" wrote: > While it's public information if the CPU in general has spectre/meltdown > bugs, it probably shouldn't be as globally obvious to all unprivileged > users As I replied to you last time you posted this a) The info is already trivially accessible via /proc/cpuinfo or by measurement to an attacker b) Some JIT and other environments need to know Alan