public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: linux-kernel@vger.kernel.org, parisc-linux@parisc-linux.org,
	Matthew Wilcox <matthew@wil.cx>,
	Grant Grundler <grundler@parisc-linux.org>
Subject: Re: [parisc-linux] Comparing PROT_EXEC-only pages on different CPUs
Date: Fri, 2 Jul 2004 05:07:52 +0100	[thread overview]
Message-ID: <20040702040752.GB10366@mail.shareable.org> (raw)
In-Reply-To: <200407020324.i623OIZ9011855@hiauly1.hia.nrc.ca>

John David Anglin wrote:
> > Richard raises an interesting point: exec-only pages are useless if
> > the code needs to read jump tables and constant pools.  It seems very
> > likely Alpha and IA64 have these.
> 
> HPPA GCC code also needs to be able to read jump tables in .text.

As Richard Henderson points out, the toolchain should be requesting
PROT_READ|PROT_EXEC if it generates code which needs data read access.
ELF is particularly good for tracking generating those flags, so do
HPPA code segments have the read flag set at the moment?  I.e. if it
does, then it would be fine to change the kernel to honour
PROT_EXEC-only.

(There's also the question of whether that code needs data read
access: do jump table instructions do data reads or do they count as
code reads?  I don't know HPPA well enough to know).

-- Jamie

  reply	other threads:[~2004-07-02  4:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 22:40 Comparing PROT_EXEC-only pages on different CPUs Jamie Lokier
2004-07-02  1:36 ` Richard Henderson
2004-07-02  4:02   ` Jamie Lokier
2004-07-02 14:51     ` Richard Curnow
2004-07-02  3:24 ` [parisc-linux] " John David Anglin
2004-07-02  4:07   ` Jamie Lokier [this message]
2004-07-03  0:39     ` John David Anglin

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=20040702040752.GB10366@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=grundler@parisc-linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=parisc-linux@parisc-linux.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