From: Kees Cook <kees.cook@canonical.com>
To: linux-kernel@vger.kernel.org
Cc: hpa@zytor.com, mingo@redhat.com, penberg@kernel.org,
alan@lxorguk.ukuu.org.uk, tglx@linutronix.de,
hpa@linux.intel.com
Subject: Re: [tip:x86/cpu] x86, cpu: Clear XD_DISABLED flag on Intel to regain NX
Date: Wed, 8 Dec 2010 14:27:13 -0800 [thread overview]
Message-ID: <20101208222713.GP5750@outflux.net> (raw)
In-Reply-To: <tip-ae84739c27b6b3725993202fe02ff35ab86468e1@git.kernel.org>
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@canonical.com>
> AuthorDate: Wed, 10 Nov 2010 10:35:52 -0800
> Committer: H. Peter Anvin <hpa@linux.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.
-Kees
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2010-12-08 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 18:35 [Security] [PATCH v5 0/4] x86: clear XD_DISABLED flag on Intel to regain NX Kees Cook
2010-11-10 18:35 ` [PATCH 1/4] x86: rename verify_cpu_64.S to verify_cpu.S Kees Cook
2010-11-10 18:35 ` [PATCH 2/4] x86: clear XD_DISABLED flag on Intel to regain NX Kees Cook
[not found] ` <tip-ae84739c27b6b3725993202fe02ff35ab86468e1@git.kernel.org>
2010-12-08 22:27 ` Kees Cook [this message]
2010-12-22 11:17 ` [tip:x86/cpu] x86, cpu: Clear " Ingo Molnar
2010-11-10 18:35 ` [PATCH 3/4] x86: call verify_cpu during 32bit CPU startup Kees Cook
2010-11-14 6:33 ` Yinghai Lu
2010-11-10 18:35 ` [PATCH 4/4] x86: only CPU features determine NX capabilities Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101208222713.GP5750@outflux.net \
--to=kees.cook@canonical.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox