[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
  • From: "Kimball Murray" <kimball.murray@xxxxxxxxx>
  • Date: Sat, 15 Dec 2007 17:46:11 -0500
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 18 Jan 2008 10:21:56 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=VStYV7Wr51D4hO/CtVIrXADPdPKNmLfxPC1xPlyr50ZuryDDHmff/nfY1xP/uzYFVPRkdWM/ICe1cWKatZuCw0JkohDVHgjvJOQ8FV0kt/3RGNeG7gOxK3CjpYh70ERkFQcYbz8EadT1kxIVZWW1JH0k8cmVzuJltbKSBfqDxI0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Works fine, thanks!


On Dec 15, 2007 1:30 PM, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> On 14/12/07 23:48, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx> 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.
>
> Please try c/s 16624 in the staging tree
> (http://xenbits.xensource.com/staging/xen-unstable.hg).
>
>  -- Keir
>
>
>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.