From: Jamie Lokier <jamie@shareable.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>,
wesolows@foobazco.org, sparclinux@vger.kernel.org,
ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: A question about PROT_NONE on Sparc and Sparc64
Date: Wed, 30 Jun 2004 22:52:20 +0000 [thread overview]
Message-ID: <20040630225220.GA32560@mail.shareable.org> (raw)
In-Reply-To: <20040630135419.25b843b8.davem@redhat.com>
David S. Miller wrote:
> On Wed, 30 Jun 2004 04:28:05 -0400
> Jakub Jelinek <jakub@redhat.com> wrote:
>
> > I believe R!X and X!R pages ought to be possible on sparc64 too,
> > just use a different bit as "read" in the fast ITLB miss handler
> > from the one fast DTLB miss uses.
>
> That's correct. But I have no plans to implement this
> any time soon :-)
The PaX security patch already implements R!X pages on Sparc64, so you
could just cut out that part of the patch. Just pick out the changes
to arch/sparc64/* and include/asm-sparc64/*:
http://pax.grsecurity.net/pax-linux-2.6.7-200406252135.patch
It appears to use exactly the technique Jakub describes, and has been tested.
-- Jamie
WARNING: multiple messages have this Message-ID (diff)
From: Jamie Lokier <jamie@shareable.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>,
wesolows@foobazco.org, sparclinux@vger.kernel.org,
ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: A question about PROT_NONE on Sparc and Sparc64
Date: Wed, 30 Jun 2004 23:52:20 +0100 [thread overview]
Message-ID: <20040630225220.GA32560@mail.shareable.org> (raw)
In-Reply-To: <20040630135419.25b843b8.davem@redhat.com>
David S. Miller wrote:
> On Wed, 30 Jun 2004 04:28:05 -0400
> Jakub Jelinek <jakub@redhat.com> wrote:
>
> > I believe R!X and X!R pages ought to be possible on sparc64 too,
> > just use a different bit as "read" in the fast ITLB miss handler
> > from the one fast DTLB miss uses.
>
> That's correct. But I have no plans to implement this
> any time soon :-)
The PaX security patch already implements R!X pages on Sparc64, so you
could just cut out that part of the patch. Just pick out the changes
to arch/sparc64/* and include/asm-sparc64/*:
http://pax.grsecurity.net/pax-linux-2.6.7-200406252135.patch
It appears to use exactly the technique Jakub describes, and has been tested.
-- Jamie
next prev parent reply other threads:[~2004-06-30 22:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 3:05 A question about PROT_NONE on Sparc and Sparc64 Jamie Lokier
2004-06-30 3:05 ` Jamie Lokier
2004-06-30 5:17 ` David S. Miller
2004-06-30 5:17 ` David S. Miller
2004-06-30 5:17 ` David S. Miller
2004-06-30 15:21 ` wesolows
2004-06-30 15:21 ` wesolows
2004-06-30 8:28 ` Jakub Jelinek
2004-06-30 8:28 ` Jakub Jelinek
2004-06-30 20:54 ` David S. Miller
2004-06-30 20:54 ` David S. Miller
2004-06-30 22:52 ` Jamie Lokier [this message]
2004-06-30 22:52 ` Jamie Lokier
2004-07-01 5:25 ` David S. Miller
2004-07-01 5:25 ` David S. Miller
2004-07-01 7:47 ` David S. Miller
2004-07-01 7:47 ` David S. Miller
2004-07-02 1:03 ` A question about PROT_NONE on Sun4c 32-bit Sparc Jamie Lokier
2004-07-02 1:03 ` Jamie Lokier
2004-07-02 4:11 ` Keith M. Wesolowski
2004-07-02 4:11 ` Keith M. Wesolowski
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=20040630225220.GA32560@mail.shareable.org \
--to=jamie@shareable.org \
--cc=davem@redhat.com \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=ultralinux@vger.kernel.org \
--cc=wesolows@foobazco.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.