linux-kernel - Re: [tip:x86/cpu] x86, cpu: Clear XD_DISABLED flag on Intel to regain NX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20101222111725.GD3127@elte.hu>
Date:	Wed, 22 Dec 2010 12:17:25 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Kees Cook <kees.cook@...onical.com>
Cc:	linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
	penberg@...nel.org, alan@...rguk.ukuu.org.uk, tglx@...utronix.de,
	hpa@...ux.intel.com
Subject: Re: [tip:x86/cpu] x86, cpu: Clear XD_DISABLED flag on Intel to
 regain NX


* Kees Cook <kees.cook@...onical.com> wrote:

> On Thu, Nov 11, 2010 at 02:49:04AM +0000, tip-bot for Kees Cook wrote:
> > Commit-ID:  ae84739c27b6b3725993202fe02ff35ab86468e1
> > Gitweb:     http://git.kernel.org/tip/ae84739c27b6b3725993202fe02ff35ab86468e1
> > Author:     Kees Cook <kees.cook@...onical.com>
> > AuthorDate: Wed, 10 Nov 2010 10:35:52 -0800
> > Committer:  H. Peter Anvin <hpa@...ux.intel.com>
> > CommitDate: Wed, 10 Nov 2010 15:42:54 -0800
> > 
> > x86, cpu: Clear XD_DISABLED flag on Intel to regain NX
> 
> Just some quick positive feedback on this patch series: I've had at least one 
> confirmed report of a user with an Asus system that had NX disabled (in the BIOS 
> which offered no toggle to switch it on) is able to use the NX bit on their CPU 
> finally. Additionally, no regressions have been identified either, and there has 
> been a fair number of people running with the patch for a few weeks now in 
> Ubuntu's development kernel.

Nice!

	Ingo
--
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/