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] Xen 4.0.0x allows for data corruption in Dom0

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 4.0.0x allows for data corruption in Dom0
From: Joanna Rutkowska <joanna@xxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 09 Mar 2010 01:20:57 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 08 Mar 2010 16:21:33 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=message-id:date:from:mime-version:to:cc:subject:references:in-reply-to:content-type; s=smtpout; bh=bu25FMfCg5sfxpjW9DS0FZVRNYA=; b=b4f1PmFtfZ7KUdDwD6QctudY2Ss0CwHHrnp6dZ39hs5yWF8vJ+bxjsJSr7al43d14mATGi99KtYQhwU7sdRMcmvjeBcVpkYapzxNrH6G8QvVfTPz3NP0HKy3paQoNj+VK1GcGWhR6yaoalXk+mt90Bpi/ke4Nttae+gSvJMfsSo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01918C59@trantor>
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: <4B922A89.2060105@xxxxxxxxxxxxxxxxxxxxxx><4B957914.4050408@xxxxxxxx><4B957B93.4060401@xxxxxxxxxxxxxxxxxxxxxx><4B958475.3050407@xxxxxxxx> <4B9586E0.2060005@xxxxxxxxxxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01918C59@trantor>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100301 Fedora/3.0.3-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.3
On 03/09/2010 01:18 AM, James Harper wrote:
>>> I can't think of a Xen failure-mode which would cause these symptoms
>>> without also being massively obvious in other cases.  (But "I can't
>>> think of..." is where all the best bugs hide.)
>> But the corruptions always happen in 32-bytes chunks, which might
>> suggest it's not a page-related problem (e.g. wrongly re-used page),
> as
>> in that case we would be observing (at least sometimes) much bigger
>> chunks of corrupted data, I think.
> Based on your hex dump output, it appears to be the first 32 bytes of a
> page, which does lend itself to the idea that it's a page allocated for
> something with only the first 32 bytes used.
> You've stated that you are no longer set up to reproduce it, which is
> unfortunate. If you find yourself in a position to try it again there
> are bunch of things you could try to figure out on which end of the copy
> the problem lies.
But everybody can try it with the kernels I provided, right? I'm not the
only one person, who can do this...


Attachment: signature.asc
Description: OpenPGP digital signature

Xen-devel mailing list