From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: race between kvm-kmod-3.0 and kvm-kmod-3.3 // was: race condition in qemu-kvm-1.0.1 Date: Tue, 03 Jul 2012 16:13:04 +0300 Message-ID: <4FF2EFE0.2090400@redhat.com> References: <4FEB2945.1030607@dlhnet.de> <4FEB3AC6.6010206@web.de> <4FEC1FC9.7050103@dlhnet.de> <4FEC2210.1030005@siemens.com> <4FEC2475.4030202@dlhnet.de> <4FEC2626.90402@dlhnet.de> <4FF1B8A6.2020101@redhat.com> <4FF2ED2A.7080300@dlhnet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , qemu-devel@nongnu.org, kvm@vger.kernel.org, Gleb Natapov To: Peter Lieven Return-path: Received: from mx1.redhat.com ([209.132.183.28]:40486 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751998Ab2GCNNM (ORCPT ); Tue, 3 Jul 2012 09:13:12 -0400 In-Reply-To: <4FF2ED2A.7080300@dlhnet.de> Sender: kvm-owner@vger.kernel.org List-ID: On 07/03/2012 04:01 PM, Peter Lieven wrote: > Further output from my testing. > > Working: > Linux 2.6.38 with included kvm module > Linux 3.0.0 with included kvm module > > Not-Working: > Linux 3.2.0 with included kvm module > Linux 2.6.28 with kvm-kmod 3.4 > Linux 3.0.0 with kvm-kmod 3.4 > Linux 3.2.0 with kvm-kmod 3.4 > > I can trigger the race with any of qemu-kvm 0.12.5, 1.0 or 1.0.1. > It might be that the code was introduced somewhere between 3.0.0 > and 3.2.0 in the kvm kernel module and that the flaw is not > in qemu-kvm. > > Any hints? > A bisect could tell us where the problem is. To avoid bisecting all of linux, try git bisect v3.2 v3.0 virt/kvm arch/x86/kvm -- error compiling committee.c: too many arguments to function