linux-kernel - RE: [PATCH] x86: Configure NX support earlier in setup

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <8B2F6FFD0BD1E448853114367400A3730702007151@BLRX7MCDC203.AMER.DELL.COM>
Date:	Thu, 13 Nov 2014 19:10:12 +0530
From:	<B_B_Singh@...L.com>
To:	<bp@...e.de>
CC:	<stuart.w.hayes@...il.com>, <hpa@...or.com>, <tglx@...utronix.de>,
	<mingo@...hat.com>, <x86@...nel.org>,
	<linux-kernel@...r.kernel.org>, <matt.fleming@...el.com>,
	<jkosina@...e.cz>
Subject: RE: [PATCH] x86: Configure NX support earlier in setup_arch


> -----Original Message-----
> From: Borislav Petkov [mailto:bp@...e.de]
> Sent: Thursday, November 13, 2014 6:01 PM
> To: Singh, B B
> Cc: stuart.w.hayes@...il.com; hpa@...or.com; tglx@...utronix.de;
> mingo@...hat.com; x86@...nel.org; linux-kernel@...r.kernel.org;
> matt.fleming@...el.com; Jiri Kosina
> Subject: Re: [PATCH] x86: Configure NX support earlier in setup_arch
> 
> On Thu, Nov 13, 2014 at 12:09:02PM +0530, B_B_Singh@...L.com wrote:
> > I feel this can be a valid scenario where user wants to disable the
> > memory protection (NX flag disable) for his requirement, in that case
> > he will hit this issue. So request you to please revisit this patch.
> 
> First of all, please do not top-post. Here's why:
> 
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
> 

Sorry Boris, will make note on this & follow the same.

> Revisit this patch how? I'm not sure I understand...

I got an answer from Thomas, will check with BIOS team & come back. 

Thanks
Balaji Singh