Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755411Ab0KJShJ (ORCPT ); Wed, 10 Nov 2010 13:37:09 -0500 Received: from smtp.outflux.net ([198.145.64.163]:46672 "EHLO smtp.outflux.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752484Ab0KJShH (ORCPT ); Wed, 10 Nov 2010 13:37:07 -0500 From: Kees Cook To: x86@kernel.org, linux-kernel@vger.kernel.org Cc: Pekka Enberg , Alan Cox , Ingo Molnar Subject: [Security] [PATCH v5 0/4] x86: clear XD_DISABLED flag on Intel to regain NX Date: Wed, 10 Nov 2010 10:35:50 -0800 Message-Id: <1289414154-7829-1-git-send-email-kees.cook@canonical.com> X-Mailer: git-send-email 1.7.2.3 X-HELO: www.outflux.net Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1284 Lines: 31 Resending with Alan Cox's Acks, at Ingo's request. Intel CPUs have an additional MSR bit to indicate if the BIOS was configured to disable NX. This bit was traditionally used for operating systems that did not understand how to handle the NX bit. Since Linux understands this, this BIOS flag should be ignored by default. In a review[1] of reported hardware being used by Ubuntu bug reporters, almost 10% of systems had an incorrectly configured BIOS, leaving their systems unable to use the NX features of their CPU. This change will clear the MSR_IA32_MISC_ENABLE_XD_DISABLE bit so that NX cannot be inappropriately controlled by the BIOS on Intel CPUs. If, under very strange hardware configurations, NX actually needs to be disabled, "noexec=off" can be used to restore the prior behavior. -Kees [1] http://www.outflux.net/blog/archives/2010/02/18/data-mining-for-nx-bit/ --- Changelog: v2 - rearranged use of verify_cpu() v3 - resent, show stats on systems that need it v4 - expanded commit messages, added acks v5 - added acks -- 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/