From: David Woodhouse <dwmw2@infradead.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: 32 bit userland on G5
Date: Wed, 14 Jun 2006 00:31:49 +0100 [thread overview]
Message-ID: <1150241510.11159.159.camel@shinybook.infradead.org> (raw)
In-Reply-To: <17551.16830.186314.247458@cargo.ozlabs.ibm.com>
On Wed, 2006-06-14 at 08:52 +1000, Paul Mackerras wrote:
> Historically the PPC32 ELF ABI has used an executable PLT, containing
> instructions constructed at runtime, located next to the BSS, and
> without the corresponding program header entry indicating execute
> permission. Alan Modra devised a new way of doing the PLT which
> doesn't require it to be executable, but of course it is only used in
> programs that have been built since the new method went into the
> toolchain (in fact all of the .o files being linked have to have been
> compiled with the new method in order for it to be used).
'Historical' being until about 4 years ago, around the time of
http://ecos.sourceware.org/ml/binutils/2002-05/msg00097.html ?
> So if you are absolutely sure that every program you will ever want to
> run on your kernel has been built with an up-to-date toolchain, you
> can turn on enforcement of execute permissions for 32-bit processes.
> It would be a "courageous" step (in the Yes Minister sense :) for a
> distro to do it, IMHO.
We already did it in Fedora. We don't default to READ_IMPLIES_EXEC for
32-bit processes on the 64-bit kernel.
--
dwmw2
next prev parent reply other threads:[~2006-06-13 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 10:25 32 bit userland on G5 Johannes Berg
2006-06-13 12:45 ` David Woodhouse
2006-06-13 16:05 ` Johannes Berg
2006-06-13 16:15 ` David Woodhouse
2006-06-13 16:18 ` Johannes Berg
2006-06-13 22:52 ` Paul Mackerras
2006-06-13 23:31 ` David Woodhouse [this message]
2006-06-13 23:46 ` Paul Mackerras
2006-06-14 0:04 ` David Woodhouse
2006-06-13 22:44 ` Paul Mackerras
2006-06-14 8:35 ` Johannes Berg
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=1150241510.11159.159.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=johannes@sipsolutions.net \
--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 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).