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] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages
From: Thomas Schwinge <thomas@xxxxxxxxxxxxx>
Date: Tue, 20 Apr 2010 13:18:18 +0200
Cc: Ian Campbell <ijc@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Tue, 20 Apr 2010 04:19:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BC1013D.2020003@xxxxxxxx>
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>
References: <20100408113422.GD4183@xxxxxxxxxxxxxxxxxxxxxxxxxx> <20100408133820.GA29832@xxxxxxxxxxxxxxxxxxx> <20100408221953.GG4183@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4BBE5DF2.6040707@xxxxxxxx> <20100409180016.GA14029@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4BBF7004.8000707@xxxxxxxx> <20100410221349.GM4183@xxxxxxxxxxxxxxxxxxxxxxxxxx> <4BC1013D.2020003@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)

On Sat, Apr 10, 2010 at 03:52:45PM -0700, Jeremy Fitzhardinge wrote:
> On 04/10/2010 03:13 PM, Thomas Schwinge wrote:
> >> Normally that would be OK, because it uses:
> >>
> >>    __get_user(pfn, &machine_to_phys_mapping[mfn]);
> >>
> >> to dereference the array.  But at this early stage, none of the kernel's
> >> exception handlers have been set up, so this will just fault into Xen.
> >>
> >> It would be interesting to confirm this by building your kernel with
> >> CONFIG_DEBUG_INFO=y in the .config, and verify that the faulting
> >> instruction is actually this line.
> >>     
> > Bingo!
> Excellent.  Now I just need to work out how to do a proper manual limit
> check on the mfn.  (I've always been a bit suspicious of this code,
> because there's no guarantee that a random invalid mfn *won't* happen to
> return the pfn we're looking for...)

Any news already about this one?


Attachment: signature.asc
Description: Digital signature

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>