From: Stuart Hayes <stuart.w.hayes@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org, matt.fleming@intel.com, bp@suse.de
Subject: Re: [PATCH] x86: Configure NX support earlier in setup_arch
Date: Wed, 09 Jul 2014 19:56:29 -0500 [thread overview]
Message-ID: <53BDE4BD.50605@gmail.com> (raw)
In-Reply-To: <53BC72D8.4090705@zytor.com>
On 7/8/2014 5:38 PM, H. Peter Anvin wrote:
> On 07/08/2014 03:34 PM, Stuart Hayes wrote:
>>
>> I haven't received any responses... is there a problem with the patch? Also CCing a couple people.
>>
>
> I was on vacation last week and am still catching up.
>
> It would also help if you describe the real-world scenario that made you
> trip over this.
>
> -hpa
>
Well... I got this issue because a co-worker tripped over it. He had NX disabled in BIOS for some reason, and found that linux wouldn't boot--it hung right after grub2. I guess it took a while to figure out that it was the fact that NX was disabled that caused linux not to come up--and that could happen to other people. I don't know of any real-world scenarios in which someone would actually prefer to run a recent linux kernel with NX disabled, though.
It looks like some of the other boot paths into the kernel automatically clear the XD_DISABLE bit in the MISC_ENABLE MSR in the CPU (in verify_cpu), but that doesn't happen when grub2 jumps to startup_64 in arch/x86/boot/compressed/head_64.S. I guess instead of this patch, I could try to make a patch that turns NX back on (somewhere in startup_64), but since the kernel already supports NX being disabled, so I thought maybe just fixing that would be better. I didn't like seeing the kernel just die without giving any indication of what the problem is.
Stuart
next prev parent reply other threads:[~2014-07-10 0:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 1:47 [PATCH] x86: Configure NX support earlier in setup_arch Stuart Hayes
2014-07-08 22:34 ` Stuart Hayes
2014-07-08 22:38 ` H. Peter Anvin
2014-07-10 0:56 ` Stuart Hayes [this message]
2014-07-14 17:22 ` Borislav Petkov
2014-07-14 17:28 ` H. Peter Anvin
2014-07-14 17:35 ` Borislav Petkov
2014-11-13 6:39 ` B_B_Singh
2014-11-13 12:30 ` Borislav Petkov
2014-11-13 13:40 ` B_B_Singh
2014-11-13 15:48 ` Thomas Gleixner
2014-11-13 12:54 ` Thomas Gleixner
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=53BDE4BD.50605@gmail.com \
--to=stuart.w.hayes@gmail.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).