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  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]
Date:	Tue, 20 Oct 2009 11:18:43 +0900
From:	"H. Peter Anvin" <>
To:	Kees Cook <>
CC:	Arjan van de Ven <>,
	Thomas Gleixner <>,
	Ingo Molnar <>,,
	Pekka Enberg <>,
	Jan Beulich <>,
	Vegard Nossum <>,
	Yinghai Lu <>,
	Jeremy Fitzhardinge <>,
Subject: Re: [PATCH v2] [x86] detect and report lack of NX protections

On 10/20/2009 11:04 AM, Kees Cook wrote:
> It is possible for x86_64 systems to lack the NX bit (see check_efer())
> either due to the hardware lacking support or the BIOS having turned
> off the CPU capability, so NX status should be reported.  Additionally,
> anyone booting NX-capable CPUs in 32bit mode without PAE will lack NX
> functionality, so this change provides feedback for that case as well.
> v2: use "Alert:" instead of "Warning:" to avoid confusiong with WARN_ON()

They're both wrong.  Both imply that the user needs to take an action, 
which is wrong because the kernel is working as intended.  If you need 
to use any kind of alert word, it should be something like "Notice:", 
and it should be KERN_NOTICE or even KERN_INFO.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists