From: David Gibson <david@gibson.dropbear.id.au>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] Allow exec on 32-bit from readable, non-exec pages, with a warning.
Date: Tue, 17 Jul 2007 12:42:46 +1000 [thread overview]
Message-ID: <20070717024246.GA6482@localhost.localdomain> (raw)
In-Reply-To: <89E626D4-D48D-4062-A996-E2DFFE8248E3@kernel.crashing.org>
On Wed, Jul 11, 2007 at 02:03:24AM +0200, Segher Boessenkool wrote:
> >> Yeah. Giving the warning is a good thing though.
> >
> > No, it isn't; it's just noise, if we're not ever going to do anything
> > to prevent the behaviour - and we can't.
>
> The same userland code will not run correctly on PPC64 or BookE
> systems. Is that not a reason to warn?
Way back when, I distinctly recall aborting my plans to implement
per-page exec on 40x, precisely because of executables like this.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-07-17 2:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 19:57 [PATCH] Allow exec on 32-bit from readable, non-exec pages, with a warning Scott Wood
2007-07-09 20:25 ` Arnd Bergmann
2007-07-09 21:16 ` Scott Wood
2007-07-09 20:52 ` Arnd Bergmann
2007-07-09 21:29 ` Linas Vepstas
2007-07-09 21:32 ` Scott Wood
2007-07-10 13:08 ` Segher Boessenkool
2007-07-10 23:29 ` Paul Mackerras
2007-07-11 0:03 ` Segher Boessenkool
2007-07-11 1:02 ` Paul Mackerras
2007-07-17 2:42 ` David Gibson [this message]
2007-07-17 15:18 ` Segher Boessenkool
2007-07-17 16:30 ` Kumar Gala
2007-07-17 16:37 ` Segher Boessenkool
2007-07-10 13:11 ` Segher Boessenkool
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=20070717024246.GA6482@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.