This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)

To: "Christopher S. Aker" <caker@xxxxxxxxxxxx>, xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 16 Jul 2009 18:05:18 +0100
Delivery-date: Thu, 16 Jul 2009 10:09:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A5F537A.8030705@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoGMZ3lkJdKdB/nRdCqYilwsc86rgABfpNg
Thread-topic: [Xen-devel] d273:v3: reserved bit in page table (ec=0019)
User-agent: Microsoft-Entourage/
On 16/07/2009 17:21, "Christopher S. Aker" <caker@xxxxxxxxxxxx> wrote:

> Xen 3.3-testing @ changeset 18651, 64bit
> dom0 @ changeset 888, PAE
> Files: http://theshore.net/~caker/xen/BUGS/1.22/
> (XEN) d273:v3: reserved bit in page table (ec=0019)

Unexpected page fault due to a reserved bit set in a guest page directory

> (XEN) Pagetable walk from 00000000c0101347:
> (XEN)  L4[0x000] = 000000067c36a027 0000000000016495
> (XEN)  L3[0x003] = 000000067c06c027 0000000000016793
> (XEN)  L2[0x000] = 00001f5e9d00f403 ffffffffffffffff
Bogus PDE -- the bottom 12 bits are potentially okay (although I don't think
Linux uses the _PAGE_AVAIL bits) but the physical address is definitely
bogus. Begs the question where the bogus PDE came from of course, since that
would be the actual bug. The crash report here is the symptom when the PDE
actually next gets used.

 -- Keir

Xen-devel mailing list