From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Aurelien Jarno <aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Data corruption in guest using KVM
Date: Mon, 23 Jul 2007 11:04:30 +0300 [thread overview]
Message-ID: <46A4610E.4040107@qumranet.com> (raw)
In-Reply-To: <20070722233429.GA10146-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
Aurelien Jarno wrote:
> I have tried this branch, and the data get corrupted another way. This
> is due to the fact that the source address is not incremented for the
> second write. The patch below fixes that.
>
> With this patch, I haven't be able to make any corruption. I have added
> a printk in the code to see that I have been able to trigger 21
> cross-boundary writes without any problem in the various guests.
>
> So I think this bug is now fixed. Thanks for your help.
>
Thanks for the fix, and for such a good report and testing.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-07-23 8:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 17:22 Data corruption in guest using KVM Aurelien Jarno
[not found] ` <20070721172248.GA1555-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-21 17:46 ` Anthony Liguori
[not found] ` <46A24675.1010506-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-07-21 17:54 ` Aurelien Jarno
[not found] ` <20070721175404.GA3665-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-21 18:03 ` Anthony Liguori
[not found] ` <46A24A7E.6040104-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-07-21 18:39 ` Aurelien Jarno
[not found] ` <20070721183924.GA5108-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-21 21:00 ` Missing my posts to this lists Simon Gao
[not found] ` <46A273F4.2040001-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
2007-07-22 7:53 ` Avi Kivity
2007-07-22 7:52 ` Data corruption in guest using KVM Avi Kivity
[not found] ` <46A30CA3.3090100-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-22 13:38 ` Aurelien Jarno
[not found] ` <20070722133818.GG16993-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-22 13:46 ` Avi Kivity
[not found] ` <46A35FAB.701-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-22 16:44 ` Aurelien Jarno
[not found] ` <20070722164454.GA26166-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-22 17:34 ` Avi Kivity
[not found] ` <46A3952D.2020009-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-22 18:14 ` Aurelien Jarno
2007-07-22 23:34 ` Aurelien Jarno
[not found] ` <20070722233429.GA10146-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-23 6:08 ` Aurelien Jarno
2007-07-23 8:04 ` Avi Kivity [this message]
2007-07-22 15:14 ` Avi Kivity
[not found] ` <46A37448.1010008-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-22 15:19 ` Aurelien Jarno
[not found] ` <20070722151913.GA22621-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-22 15:24 ` Avi Kivity
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=46A4610E.4040107@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.