public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Pawe?? Sikora <pluto@pld-linux.org>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PROPOSAL/PATCH] Remove PT_GNU_STACK support before 2.6.11
Date: Sun, 6 Feb 2005 19:38:34 +0100	[thread overview]
Message-ID: <20050206183834.GC18245@wotan.suse.de> (raw)
In-Reply-To: <200502061907.28165.pluto@pld-linux.org>

> [1] glibc-2.3.4 kill buggy bins at the load time.
>     (please look into: elf/dl-load.c, elf/dl-support.c, elf/rtld.c)

I don't see how that can work for arbitary code executed in some
arbitary mmap. 

Please explain.

>     This works on i386/PaX systems too (hardware NX isn't required).

But it's for the 99.99999% of other users who don't use such
weird third party patches.

> The execstack req. disappeard (~99% of broken sources).

My problem is basically that the effort of fixing these
sources seems to be shifted to x86-64 now in mainstream
linux. And I don't like that.

-Andi

      reply	other threads:[~2005-02-06 18:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06 11:36 [PROPOSAL/PATCH] Remove PT_GNU_STACK support before 2.6.11 Andi Kleen
2005-02-06 11:47 ` Arjan van de Ven
2005-02-06 12:02   ` Ingo Molnar
2005-02-06 12:25     ` Ingo Molnar
2005-02-06 12:36     ` Andi Kleen
2005-02-06 12:45     ` Ingo Molnar
2005-02-06 12:50       ` Andi Kleen
2005-02-06 12:59         ` Arjan van de Ven
2005-02-06 13:01           ` Andi Kleen
2005-02-06 13:04             ` Arjan van de Ven
2005-02-06 13:09               ` Andi Kleen
2005-02-06 13:31                 ` Ingo Molnar
2005-02-06 13:43                   ` Andi Kleen
2005-02-06 13:06             ` Christoph Hellwig
2005-02-06 13:11               ` Andi Kleen
2005-02-06 13:32                 ` Ingo Molnar
2005-02-06 13:46                   ` Andi Kleen
2005-02-06 14:08                     ` Ingo Molnar
2005-02-06 14:22                       ` Ingo Molnar
2005-02-06 14:29                       ` Andi Kleen
2005-02-06 17:08                         ` Linus Torvalds
2005-02-06 17:13                           ` Arjan van de Ven
2005-02-06 17:31                             ` Linus Torvalds
2005-02-06 17:39                               ` Arjan van de Ven
2005-02-06 18:04                                 ` Linus Torvalds
2005-02-06 18:08                                   ` Arjan van de Ven
2005-02-06 17:56                           ` Andi Kleen
2005-02-06 12:33   ` Andi Kleen
2005-02-06 12:40     ` Arjan van de Ven
2005-02-06 12:48       ` Andi Kleen
2005-02-06 15:54         ` Andreas Schwab
2005-02-06 17:05     ` Linus Torvalds
2005-02-06 17:58       ` Andi Kleen
2005-02-06 12:11 ` Paweł Sikora
     [not found] ` <200502061303.12377.pluto@pld-linux.org>
     [not found]   ` <20050206124701.GD30109@wotan.suse.de>
2005-02-06 18:07     ` Paweł Sikora
2005-02-06 18:38       ` Andi Kleen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050206183834.GC18245@wotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pluto@pld-linux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox