From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: gate page oops
Date: Fri, 29 Apr 2005 11:42:08 +0000 [thread overview]
Message-ID: <17010.7568.775064.65612@napali.hpl.hp.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504221524590.31361@dhcp83-105.boston.redhat.com>
>>>>> On Tue, 26 Apr 2005 13:10:06 -0400 (EDT), Jason Baron <jbaron@redhat.com> said:
Jason> On Fri, 22 Apr 2005, Luck, Tony wrote:
>> The gate page only needs to be PAGE_SIZE ... doesn't it?
Jason> I'm not really sure...i was hoping somebody on the list would
Jason> know :) If you look at setup_gate(), it establishes two gate
Jason> pages, the comment says:
Jason> * Map the gate page twice: once read-only to export the ELF
Jason> headers etc. and once * execute-only page to enable
Jason> privilege-promotion via "epc":
Jason> So the patch i proposed was intended to allow user access to
Jason> these two regions. Currently, that isn't being done properly,
Jason> leading to an oops.
Yes, IIRC, we need to give ptrace() access to the execute-only page so
that a debugger can read and decode the instruction at the address
(yes, that circumvents the execute-only part of the mapping, but we
don't really care about that; the only reason it's execute-only is
because that's the only way to get the promote-privilege-on-epc
behavior).
--david
next prev parent reply other threads:[~2005-04-29 11:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 19:35 gate page oops Jason Baron
2005-04-22 20:52 ` Luck, Tony
2005-04-26 17:10 ` Jason Baron
2005-04-29 11:42 ` David Mosberger [this message]
2005-05-03 20:47 ` Jason Baron
2005-06-07 0:06 ` David Mosberger
2005-06-08 5:18 ` David Mosberger
2005-06-08 15:49 ` Jason Baron
2005-06-08 17:11 ` Luck, Tony
2005-06-08 17:23 ` David Mosberger
2005-06-08 17:44 ` David Mosberger
2005-06-09 17:48 ` Luck, Tony
2005-06-09 17:51 ` David Mosberger
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=17010.7568.775064.65612@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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