From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Data corruption in guest using KVM Date: Mon, 23 Jul 2007 11:04:30 +0300 Message-ID: <46A4610E.4040107@qumranet.com> References: <20070721172248.GA1555@hall.aurel32.net> <46A30CA3.3090100@qumranet.com> <20070722133818.GG16993@hall.aurel32.net> <46A35FAB.701@qumranet.com> <20070722164454.GA26166@hall.aurel32.net> <46A3952D.2020009@qumranet.com> <20070722233429.GA10146@hall.aurel32.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Aurelien Jarno Return-path: In-Reply-To: <20070722233429.GA10146-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.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/