From: Johannes Berg <johannes@sipsolutions.net>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: 32 bit userland on G5
Date: Tue, 13 Jun 2006 12:25:48 +0200 [thread overview]
Message-ID: <1150194348.9208.33.camel@johannes> (raw)
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
Hi,
Since apparently the G5 honours no-execute permissions, shouldn't the 64
bit kernel set the READ_IMPLIES_EXEC personality flag for 32-bit
userland?
The memory being execute-protected is causing a mono bug
(http://bugzilla.ximian.com/show_bug.cgi?id=77028) but I'm not sure
where the correct fix would be, currently the kernel doesn't seem to be
behaving exactly the same on G4 and G5.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
next reply other threads:[~2006-06-13 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 10:25 Johannes Berg [this message]
2006-06-13 12:45 ` 32 bit userland on G5 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
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=1150194348.9208.33.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.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).