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: <alpine.DEB.2.11.1411131147070.3935@nanos>
Date:	Thu, 13 Nov 2014 13:54:01 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	B_B_Singh@...L.com
cc:	bp@...e.de, stuart.w.hayes@...il.com, hpa@...or.com,
	mingo@...hat.com, x86@...nel.org, linux-kernel@...r.kernel.org,
	matt.fleming@...el.com
Subject: RE: [PATCH] x86: Configure NX support earlier in setup_arch

On Thu, 13 Nov 2014, 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.

It's not about feelings. If the user wants to disable NX he can do so
already via the kernel command line.

What that patch is useful for is to prevent an hard to debug boot
crash if the kernel happens to run on some wreckaged BIOS. But it's
not there to support and encourage braindamaged BIOS nonsense.

Thanks,

	tglx




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