From: Bill Irwin <bill.irwin@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Bill Irwin <bill.irwin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Kruchinin <dubalom@gmail.com>,
linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Andi Kleen <ak@suse.de>, Ingo Molnar <mingo@elte.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>,
wli@holomorphy.com
Subject: Re: [RFC BUG?] dereference PAGE_OFFSET address (rc7-mm2)
Date: Wed, 2 May 2007 09:32:44 -0700 [thread overview]
Message-ID: <20070502163244.GA26598@holomorphy.com> (raw)
In-Reply-To: <4638BC3E.9080708@goop.org>
Bill Irwin wrote:
>> Brain dump before crashing for the night:
>> The patch refuses to clobber already-present pagetable entries of
>> whatever origin. There are pagetables prior to this setup covering the
>> address range just above PAGE_OFFSET. If this theory is correct, you
>> should only be able to go a few MB above PAGE_OFFSET before encountering
>> unreadable kernel memory. IIRC those pagetables are a statically
>> allocated array in assembly; altering that array to set supervisor bits
>> may resolve it, though it may also be freed as initmem.
On Wed, May 02, 2007 at 09:28:46AM -0700, Jeremy Fitzhardinge wrote:
> I think this should be fixed now. Eric made all those writes
> unconditional (to fix a problem with PSE superpages not being created).
> The patch is in Andi's queue.
It needs verification with the testcase from this thread.
-- wli
next prev parent reply other threads:[~2007-05-02 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 3:26 [RFC BUG?] dereference PAGE_OFFSET address (rc7-mm2) Dan Kruchinin
2007-05-02 7:51 ` Andrew Morton
2007-05-02 8:46 ` Bill Irwin
2007-05-02 10:06 ` Bill Irwin
2007-05-02 16:28 ` Jeremy Fitzhardinge
2007-05-02 16:32 ` Bill Irwin [this message]
2007-05-02 16:51 ` Andi Kleen
2007-05-02 17:16 ` Eric W. Biederman
2007-05-02 17:52 ` Bill Irwin
2007-05-02 19:13 ` Eric W. Biederman
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=20070502163244.GA26598@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dubalom@gmail.com \
--cc=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=wli@holomorphy.com \
/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