From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753089AbbCZSfH (ORCPT ); Thu, 26 Mar 2015 14:35:07 -0400 Received: from mga03.intel.com ([134.134.136.65]:46873 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752819AbbCZSdw (ORCPT ); Thu, 26 Mar 2015 14:33:52 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,474,1422950400"; d="scan'208";a="698339572" Subject: [PATCH 08/17] x86, mpx: boot-time disable To: linux-kernel@vger.kernel.org Cc: x86@kernel.org, tglx@linutronix.de, Dave Hansen , dave.hansen@linux.intel.com From: Dave Hansen Date: Thu, 26 Mar 2015 11:33:43 -0700 References: <20150326183327.64807530@viggo.jf.intel.com> In-Reply-To: <20150326183327.64807530@viggo.jf.intel.com> Message-Id: <20150326183343.F64975EC@viggo.jf.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Dave Hansen MPX has the _potential_ to cause some issues. Say part of your init system tried to protect one of its components from buffer overflows with MPX. If there were a false positive, it's possible that MPX could keep a system from booting. MPX could also potentially cause performance issues since it is present in hot paths like the unmap path. Allow it to be disabled at boot time. Signed-off-by: Dave Hansen --- b/Documentation/kernel-parameters.txt | 4 ++++ b/arch/x86/kernel/cpu/common.c | 16 ++++++++++++++++ 2 files changed, 20 insertions(+) diff -puN arch/x86/kernel/cpu/common.c~x86-mpx-disable-boot-time arch/x86/kernel/cpu/common.c --- a/arch/x86/kernel/cpu/common.c~x86-mpx-disable-boot-time 2015-03-26 11:27:31.269400935 -0700 +++ b/arch/x86/kernel/cpu/common.c 2015-03-26 11:27:31.275401206 -0700 @@ -172,6 +172,22 @@ static int __init x86_xsaves_setup(char } __setup("noxsaves", x86_xsaves_setup); +static int __init x86_mpx_setup(char *s) +{ + /* require an exact match without trailing characters */ + if (strlen(s)) + return 0; + + /* do not emit a message if the feature is not present */ + if (!boot_cpu_has(X86_FEATURE_MPX)) + return 1; + + setup_clear_cpu_cap(X86_FEATURE_MPX); + printk("nompx: Intel Memory Protection Extensions (MPX) disabled\n"); + return 1; +} +__setup("nompx", x86_mpx_setup); + #ifdef CONFIG_X86_32 static int cachesize_override = -1; static int disable_x86_serial_nr = 1; diff -puN Documentation/kernel-parameters.txt~x86-mpx-disable-boot-time Documentation/kernel-parameters.txt --- a/Documentation/kernel-parameters.txt~x86-mpx-disable-boot-time 2015-03-26 11:27:31.272401070 -0700 +++ b/Documentation/kernel-parameters.txt 2015-03-26 11:27:31.277401296 -0700 @@ -2340,6 +2340,10 @@ bytes respectively. Such letter suffixes parameter, xsave area per process might occupy more memory on xsaves enabled systems. + nompx [X86] Disables Intel Memory Protection Extensions. + See Documentation/x86/intel_mpx.txt for more + information about the feature. + eagerfpu= [X86] on enable eager fpu restore off disable eager fpu restore _