From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51243) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XtGrh-0007oC-Tz for qemu-devel@nongnu.org; Tue, 25 Nov 2014 09:13:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XtGra-0000GP-Ad for qemu-devel@nongnu.org; Tue, 25 Nov 2014 09:13:13 -0500 Received: from mx1.redhat.com ([209.132.183.28]:36698) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XtGra-0000G9-2o for qemu-devel@nongnu.org; Tue, 25 Nov 2014 09:13:06 -0500 Date: Tue, 25 Nov 2014 09:12:56 -0500 From: Luiz Capitulino Message-ID: <20141125091256.03b81a5b@redhat.com> In-Reply-To: <1416924259.4666.38.camel@localhost.localdomain> References: <1416924259.4666.38.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Regression] hmp: QEMU crash on device_del auto-completion List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcel Apfelbaum Cc: Peter Maydell , Zhu Guihua , qemu-devel@nongnu.org, Igor Mammedov On Tue, 25 Nov 2014 16:04:19 +0200 Marcel Apfelbaum wrote: > Hi, > > The commits: > - 6a1fa9f5 (monitor: add del completion for peripheral device) > - 66e56b13 (qdev: add qdev_build_hotpluggable_device_list helper) > > cause a QEMU crash when trying to use HMP device_del auto-completion. > It can be easily reproduced by: > -enable-kvm ~/images/fedora.qcow2 -monitor stdio -device virtio-net-pci,id=vnet > (qemu) device_del /home/mapfelba/git/upstream/qemu/hw/core/qdev.c:941:qdev_build_hotpluggable_device_list: Object 0x7f6ce04e4fe0 is not an instance of type device > Aborted (core dumped) > > The root cause is qdev_build_hotpluggable_device_list going recursively over > all peripherals and their children assuming all are devices. It doesn't work > since PCI devices have at least on child which is a memory region (bus master). > > Should we try to fix it for 2.2 or simply revert it? Do you think you can post a patch in the next few days? If you can then let's try to fix it, otherwise we better revert those commits.