From: linas@austin.ibm.com (Linas Vepstas)
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, 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: Mon, 9 Jul 2007 16:29:26 -0500 [thread overview]
Message-ID: <20070709212926.GN4457@austin.ibm.com> (raw)
In-Reply-To: <4692A5B8.9010702@freescale.com>
On Mon, Jul 09, 2007 at 04:16:40PM -0500, Scott Wood wrote:
> Arnd Bergmann wrote:
> > I may be missing the obvious, but doesn't that defeat the purpose of
> > non-executable mappings?
>
> The hardware in question doesn't support non-executable mappings;
> otherwise, it'd never have worked in the first place. Note that this is
> only allowed on 32-bit, non-book-E.
>
> There isn't much value in enforcing non-exec mappings only if it happens
> to be the first fault on a given page.
Thank you. I was reading this thread last week, and scratching my head,
thinking wtf ??
--linas
next prev parent reply other threads:[~2007-07-09 21:29 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 [this message]
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
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=20070709212926.GN4457@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).