From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@ozlabs.org
Cc: paulus@samba.org
Subject: Re: [PATCH] Allow exec on 32-bit from readable, non-exec pages, with a warning.
Date: Mon, 9 Jul 2007 22:25:24 +0200 [thread overview]
Message-ID: <200707092225.25287.arnd@arndb.de> (raw)
In-Reply-To: <20070709195743.GA26089@ld0162-tx32.am.freescale.net>
On Monday 09 July 2007, Scott Wood wrote:
> In older versions of glibc (through 2.3), the dynamic linker executes a
> small amount of code from the data segment, which is not marked as
> executable. =A0A recent change (commit 9ba4ace39fdfe22268daca9f28c5df384a=
e462cf)
> stops this from working; there should be a deprecation period before
> older glibc versions stop working.
>=20
> The problem has been observed on glibc 2.2. =A0While glibc 2.3 has the sa=
me
> code, I did not see the problem; it may be that it accesses the page in
> question as data before executing from it, and thus it is already mapped.
I may be missing the obvious, but doesn't that defeat the purpose of
non-executable mappings?
Arnd <><
next prev parent reply other threads:[~2007-07-09 21:08 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 [this message]
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
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=200707092225.25287.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.