From: Jamie Lokier <jamie@shareable.org>
To: Andi Kleen <ak@suse.de>
Cc: discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: READONLY_EXEC is a curious name
Date: Wed, 14 Apr 2004 20:41:49 +0100 [thread overview]
Message-ID: <20040414194149.GF12105@mail.shareable.org> (raw)
In-Reply-To: <20040414212145.707555f6.ak@suse.de>
Andi Kleen wrote:
> > PAGE_READONLY_EXEC is defined in <asm-x86_64/pgtable.h>.
> >
> > Does anyone else think PAGE_READONLY_EXEC is an odd name for a set of
> > flags which enables read _and_ execute permission? What about
> > PAGE_READEXEC instead?
>
> It just follows the pattern there (default is with NX and _EXEC is
> the variant without NX). I don't care much either ways.
I asked because I'm about to submit a patch to clean up the Alpha
definitions and have to pick a name. I see parisc picked
PAGE_EXECREAD for this.
-- Jamie
prev parent reply other threads:[~2004-04-14 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 19:06 READONLY_EXEC is a curious name Jamie Lokier
2004-04-14 19:21 ` Andi Kleen
2004-04-14 19:41 ` Jamie Lokier [this message]
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=20040414194149.GF12105@mail.shareable.org \
--to=jamie@shareable.org \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.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