WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Xen 3.1.2 can corrupt BIOS resevered memory between 1M a

To: Kimball Murray <kimball.murray@xxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.1.2 can corrupt BIOS resevered memory between 1M and 16M.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 14 Dec 2007 23:48:54 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 14 Dec 2007 15:42:51 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bbe04eb10712141235j4264b423o61436ffd7b3c6ab4@xxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acg+q+J5ISCFIqqfEdyYUQAWy6hiGQ==
Thread-topic: [Xen-devel] Xen 3.1.2 can corrupt BIOS resevered memory between 1M and 16M.
User-agent: Microsoft-Entourage/11.3.6.070618
On 14/12/07 20:35, "Kimball Murray" <kimball.murray@xxxxxxxxx> wrote:

> So the first time through the loop, s == 1M and e == 15M.  But map_s
> gets set to 16M and then we slip into the if statement and call
> init_boot_pages with (1M, 16M), crushing the BIOS hole.

Thanks for the analysis. I'll sort out a fix and get back to you.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>