Re: [PROPOSAL/PATCH] Remove PT_GNU_STACK support before 2.6.11

[Ingo Molnar]

* Andi Kleen <ak@xxxxxxx> wrote:

> On Sun, Feb 06, 2005 at 01:06:50PM +0000, Christoph Hellwig wrote:
> > On Sun, Feb 06, 2005 at 02:01:52PM +0100, Andi Kleen wrote:
> > > > correct,
> > > > http://lists.ximian.com/archives/public/mono-list/2004-June/021592.html
> > > > 
> > > > that fixes mono instead
> > > 
> > > Silent breakage => bad.
> > 
> > silent breakage for newly compiled buggty and non-portable code.
> 
> Executing custom code in mmap is by definition non portable, 
> so this argument doesn't make very much sense.
> 
> > 
> > Still not nice but certainly tolerable.  
> 
> I strongly disagree that breaking source level compatibility silently
> like this is tolerable.
> 
> Especially since it won't even affect most users, so most developers
> won't notice it, only the x86-64 users. This makes it extremly silent
> for most people.

fortunately there's this 'NX-emulation' thing called exec-shield which
is part of Fedora (and has been part of it for almost 2 years) and did
all the testing for you on all x86 hardware, on thousands of packages
and on over a ten thousand binaries, well in advance of this going
upstream. It wasnt a bump-free ride, but it was worth it.

(the Mono bug was found this way, the Grub one wasnt, due to it being
RWE. But if it triggers it shows up immediately so it's not like you
have no sign that something wrong is going on. Only grub-install
triggers it and no boot/install kernel i know of defaults to
PAE-enabled, that's what caused grub-install being used in an NX
scenario so infrequently.)

anyway, this particular flamewar might have made more sense last Summer.

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/