xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: Xen 4.0.0x allows for data corruption in Dom0
Date: Tue, 09 Mar 2010 01:20:57 +0100	[thread overview]
Message-ID: <4B959469.7000002@invisiblethingslab.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01918C59@trantor>


[-- Attachment #1.1: Type: text/plain, Size: 1085 bytes --]

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...

j.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 226 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2010-03-09  0:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B922A89.2060105@invisiblethingslab.com>
2010-03-08 22:24 ` Xen 4.0.0x allows for data corruption in Dom0 Jeremy Fitzhardinge
2010-03-08 22:34   ` Joanna Rutkowska
2010-03-08 23:12     ` Jeremy Fitzhardinge
2010-03-08 23:23       ` Joanna Rutkowska
2010-03-08 23:41         ` Jeremy Fitzhardinge
2010-03-08 23:48           ` Joanna Rutkowska
2010-03-09  0:18         ` James Harper
2010-03-09  0:20           ` Joanna Rutkowska [this message]
2010-03-08 23:32 ` Daniel Stodden
     [not found]   ` <4B958A42.4000407@invisiblethingslab.com>
2010-03-08 23:46     ` Daniel Stodden
     [not found] <C7B80F95.C5F3%keir.fraser@eu.citrix.com>
2010-03-06 13:37 ` Joanna Rutkowska
2010-03-06 17:18   ` Keir Fraser
     [not found] <C7B7F4C4.C5D8%keir.fraser@eu.citrix.com>
2010-03-06 13:36 ` Keir Fraser
2010-03-07 14:36   ` Pasi Kärkkäinen
2010-03-07 14:39     ` Keir Fraser
2010-03-07 16:12       ` Pasi Kärkkäinen
2010-03-08 23:22         ` Daniel Stodden
2010-03-08 23:30           ` Joanna Rutkowska
2010-03-08 23:52             ` Daniel Stodden
2010-03-08 23:56               ` Joanna Rutkowska
2010-03-09  0:33                 ` Daniel Stodden
2010-03-09  8:25           ` Pasi Kärkkäinen
2010-03-09  9:37             ` Jan Beulich
2010-03-09 10:15               ` Jan Beulich
2010-03-09 10:17                 ` Keir Fraser
2010-03-09 10:15               ` Keir Fraser
2010-03-09 10:25                 ` Pasi Kärkkäinen
2010-03-09 10:43                   ` Keir Fraser
2010-03-09 12:03                     ` Pasi Kärkkäinen
2010-03-09 10:42                 ` Jan Beulich
2010-03-09 23:28                 ` Jeremy Fitzhardinge
2010-03-10  1:33                   ` Dan Magenheimer
2010-03-10 18:02                     ` Jeremy Fitzhardinge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B959469.7000002@invisiblethingslab.com \
    --to=joanna@invisiblethingslab.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).