Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936572Ab3DHXmx (ORCPT ); Mon, 8 Apr 2013 19:42:53 -0400 Received: from eddie.linux-mips.org ([78.24.191.182]:37029 "EHLO cvs.linux-mips.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760088Ab3DHXmv (ORCPT ); Mon, 8 Apr 2013 19:42:51 -0400 Date: Tue, 9 Apr 2013 00:42:49 +0100 (BST) From: "Maciej W. Rozycki" To: Kees Cook cc: Ingo Molnar , LKML , Thomas Gleixner , "H. Peter Anvin" , "x86@kernel.org" , Konrad Rzeszutek Wilk , Jeremy Fitzhardinge , Marcelo Tosatti , Alex Shi , Borislav Petkov , Alexander Duyck , Frederic Weisbecker , Steven Rostedt , "Paul E. McKenney" , "xen-devel@lists.xensource.com" , "virtualization@lists.linux-foundation.org" , "kernel-hardening@lists.openwall.com" , Dan Rosenberg , Julien Tinnes , Will Drewry , Eric Northup Subject: Re: [PATCH] x86: make IDT read-only In-Reply-To: Message-ID: References: <20130408224328.GA17641@www.outflux.net> User-Agent: Alpine 2.03 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 995 Lines: 22 On Mon, 8 Apr 2013, Kees Cook wrote: > > FWIW the change looks reasonable to me, however given that that it makes > > the arrangement unconditional and there is no longer a workaround to > > enable I think it would make sense to remove the conditional block quoted > > above altogether, along with the f00f_workaround_enabled variable itself > > (alternatively "Intel Pentium with F0 0F bug" alone could be printed > > instead and the name of the variable adjusted to make sense with the new > > meaning -- up to you to decide). > > Actually, I take it back. The other portion of the workaround is still > active (in mm/fault.c), and this chunk announces it, so I'm going to > leave it as-is. Ah, OK then. Thanks for double-checking. Maciej -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/