From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zachary Amsden Subject: Re: list_add corruption? Date: Fri, 26 Feb 2010 10:13:38 -1000 Message-ID: <4B882B72.9070406@redhat.com> References: <4B87549C.3020308@redhat.com> <4B87AE12.7010609@redhat.com> <4B87F76B.90608@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8063 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965982Ab0BZUNk (ORCPT ); Fri, 26 Feb 2010 15:13:40 -0500 Received: from int-mx08.intmail.prod.int.phx2.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o1QKDepl006112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 26 Feb 2010 15:13:40 -0500 In-Reply-To: <4B87F76B.90608@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 02/26/2010 06:31 AM, Zachary Amsden wrote: > On 02/26/2010 01:18 AM, Avi Kivity wrote: >> On 02/26/2010 06:57 AM, Zachary Amsden wrote: >>> Anyone seeing list_add corruption running qemu-kvm with -smp 2 on >>> Intel hardware? >>> >>> Debugging some local changes, which don't appear related. Running >>> module from latest git on F12. >>> >> >> Can you post a trace? Which list appears to be involved? >> > > It's the per-cpu activated vcpu list, I'm guessing, which is why I > only see it on Intel. I'm starting a bisect. I get a reliable system > crash upon release of kvm instance. :( > > Hopefully it is just a bug in my patches :) Alas, 'twere my botch.