| 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
| ||
|
Date: Sat, 11 May 2013 07:55:58 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Yuhong Bao <yuhongbao_386@...mail.com>, "mingo@...nel.org" <mingo@...nel.org>, "linux-tip-commits@...r.kernel.org" <linux-tip-commits@...r.kernel.org> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "fernando@....ntt.co.jp" <fernando@....ntt.co.jp>, "tglx@...utronix.de" <tglx@...utronix.de>, "hpa@...ux.intel.com" <hpa@...ux.intel.com> Subject: RE: [tip:x86/urgent] x86-64, init: Do not set NX bits on non-NX capable hardware Yes... But both apply. Yuhong Bao <yuhongbao_386@...mail.com> wrote: >(resending as plaintext) >> During early init, we would incorrectly set the NX bit even if the NX >> feature was not supported. Instead, only set this bit if NX is >> actually available and enabled. We already do very early detection >of >> the NX bit to enable it in EFER, this simply extends this detection >to >> the early page table mask. >AFAIK the only production x86-64 processor that don't support NX that I >know of is the original Nocona D0 stepping. >Must more common are the problem of BIOSes disabling the NX feature. > > >Yuhong Bao -- Sent from my mobile phone. Please excuse brevity and lack of formatting. -- 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/
Powered by blists - more mailing lists