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

From: Ingo Molnar (mingo_at_elte.hu)
Date: 02/06/05

  • Next message: Andi Kleen: "Re: [PROPOSAL/PATCH] Remove PT_GNU_STACK support before 2.6.11" 
    Date:	Sun, 6 Feb 2005 14:32:39 +0100
To: Andi Kleen <ak@suse.de>

    * Andi Kleen <ak@suse.de> 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@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Andi Kleen: "Re: [PROPOSAL/PATCH] Remove PT_GNU_STACK support before 2.6.11"

    Relevant Pages

    • Re: [BUG] 2.6.11- sym53c8xx Broken on pp64
      ... Are you sure it's plain 2.6.11 and not some bk clone of after 2.6.11 was ... I just found a bug in the ppc64 ioremap code that got triggered by ... the set_pte_atpatch that went into bk after 2.6.11 and that triggers ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH] fix send_sigqueue() vs thread exit race
      ... It triggers on preempt-RT and I can trigger it on vanilla SMP ... by waiting for the timer expiry in release_taskbefore the ... don't see a reason why this should not happen. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [ACPI] Re: Video memory corruption during suspend
      ... swsusp1 also triggers that. ... A plain windowmaker dekstop takes much shorter to switch. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [discuss] Re: [PATCH] adjust x86-64 watchdog tick calculation
      ... IIRC current watchdog is at one second and it ... >> still triggers even in cases when operation just takes too long. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.32-6
      ... Its just sometimes the measurements don't ... just in case it wasnt obvious ... ... setups, so i pretty much expect your setup to trigger the most problems ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)