[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100619081642.33b37676@infradead.org>
Date: Sat, 19 Jun 2010 08:16:42 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: Kees Cook <kees.cook@...onical.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Alexander Potashev <aspotashev@...il.com>,
Tim Abbott <tabbott@...lice.com>,
Sam Ravnborg <sam@...nborg.org>,
Jan Beulich <jbeulich@...ell.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/4] x86: clear XD_DISABLED flag on Intel to regain
NX
On Sat, 19 Jun 2010 10:21:29 +0200
Andi Kleen <andi@...stfloor.org> wrote:
> Kees Cook <kees.cook@...onical.com> writes:
>
> > This will clear the MSR_IA32_MISC_ENABLE_XD_DISABLE bit so that NX
> > cannot be inappropriately controlled by the BIOS on Intel CPUs. If
> > NX actually needs to be disabled, "noexec=off" can be used.
>
> The patch still seems like a bad idea to me. What happens if
> the NX bit is broken for some reason and the BIOS is right
> to disable it?
overriding the bios like this is almost always a bad idea.
(you're doing a blanket override, not a specific, verified override)
you have no idea if the SMM code can deal with NX, etc etc.
the real answer is "fix your bios setting".
Don't as owner of the machine turn something off in the bios that you
actually want.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists