From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: pci-passthrough: suspected kmemleaks Date: Mon, 20 Sep 2010 12:34:38 -0400 Message-ID: <20100920163438.GD15129@dumpdata.com> References: <294372958.20100914171732@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <294372958.20100914171732@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Sander Eikelenboom Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Tue, Sep 14, 2010 at 05:17:32PM +0200, Sander Eikelenboom wrote: > Hi Konrad, > > I encountered these suspected kmemleaks after starting a VM with pci device passed through, of which some seem potential related to pciback. Ok, most of them seem to come from arch_init_chip_data And they look to be un-used, hmm - let me put it on my todo list and see what is happening. Thanks > hex dump (first 32 bytes): > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > backtrace: > [] kmemleak_alloc+0x21/0x44 > [] __kmalloc+0x1c1/0x1ea > [] kzalloc_node+0xf/0x11 > [] get_one_free_irq_cfg+0x1a/0x45 > [] arch_init_chip_data+0x1a/0x39 > [] irq_to_desc_alloc_node+0x18d/0x1b7 > [] xen_allocate_pirq+0x99/0x185 > [] xen_register_pirq+0x3e/0x98 > [] xen_register_gsi+0x42/0xb3 > [] acpi_register_gsi+0x22/0x5f > [] acpi_pci_irq_enable+0x11f/0x212 > [] pcibios_enable_device+0x29/0x2d > [] do_pci_enable_device+0x28/0x40 > [] __pci_enable_device_flags+0x55/0x70 > [] pci_enable_device+0xe/0x10 > [] pci_enable_bridges+0x2a/0x4e