Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757143AbcKWR3W (ORCPT ); Wed, 23 Nov 2016 12:29:22 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:57873 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750997AbcKWR3U (ORCPT ); Wed, 23 Nov 2016 12:29:20 -0500 X-ME-Sender: X-Sasl-enc: fBug1Uxtd+6g9bCZd8/QN9R1BxsWSg4PHlgCBBSVPS9k 1479922159 Date: Wed, 23 Nov 2016 15:29:17 -0200 From: Henrique de Moraes Holschuh To: Borislav Petkov Cc: "Luck, Tony" , Andi Kleen , Ashok Raj , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] x86/mce: Include the PPIN in machine check records when it is available Message-ID: <20161123172916.GA19621@khazad-dum.debian.net> References: <878tsg67r3.fsf@tassilo.jf.intel.com> <1479491316-11716-1-git-send-email-tony.luck@intel.com> <20161123114855.njguoaygp3qnbkia@pd.tnic> <20161123132951.GA9373@khazad-dum.debian.net> <20161123133723.vyi7bv46h3pulldc@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161123133723.vyi7bv46h3pulldc@pd.tnic> X-GPG-Fingerprint1: 4096R/0x0BD9E81139CB4807: C467 A717 507B BAFE D3C1 6092 0BD9 E811 39CB 4807 User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1220 Lines: 32 On Wed, 23 Nov 2016, Borislav Petkov wrote: > On Wed, Nov 23, 2016 at 11:29:51AM -0200, Henrique de Moraes Holschuh wrote: > > 1. Assuming we can do it, always lock it when it is found to be unlocked > > at kernel boot. > > Because...? Privacy, and the fact that /dev/cpu/msr exists and is enabled on almost all general-use distros. > > 2. Not attempt to change its state from disabled to enabled *unless* > > given a command line parameter authorizing it. A kconfig-based > > solution for default+command line override would also work well IMHO, > > if it makes more sense. > > You can't reenable it: Yeah, I just found the description for that thing in the IA32 manual. It can be disabled + unlocked, disabled + locked, or enabled + unlocked. Once locked, it will stay disabled until the next reboot. However, the manual makes it clear we are _not_ supposed to leave it enabled + unlocked. Apparently, we're supposed to do our business and disable+lock it (i.e. enable, read and store/process, disable+lock). Looks like it is supposed to be used in a way that protects privacy by making it very hard for general use software to depend on it existing and being enabled. -- Henrique Holschuh