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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 10 Nov 2009 14:47:20 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Willy Tarreau <w@....eu> CC: Ingo Molnar <mingo@...e.hu>, Pavel Machek <pavel@....cz>, Avi Kivity <avi@...hat.com>, Alan Cox <alan@...rguk.ukuu.org.uk>, Matteo Croce <technoboy85@...il.com>, Sven-Haegar Koch <haegar@...net.de>, linux-kernel@...r.kernel.org Subject: Re: i686 quirk for AMD Geode On 11/10/2009 02:42 PM, Willy Tarreau wrote: > On Tue, Nov 10, 2009 at 11:20:31PM +0100, Ingo Molnar wrote: >> >> * H. Peter Anvin <hpa@...or.com> wrote: >> >>> *THIS* is the kind of complexity that makes me think that having a >>> single source for all interpretation done in the kernel is the >>> preferred option. >> >> Definitely agreed ... The NX code is quite a maze right now, so changes >> to it should come generously laced with cleanups. > > BTW, I don't see why we should be impacted by NX. Trying to > execute from an NX page would return a SEGV, not SIGILL, so > we should not be bothered, am I wrong ? Yes. Consider a page-crossing instruction. -hpa -- 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