WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: pci-passthrough: suspected kmemleaks

To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: pci-passthrough: suspected kmemleaks
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 20 Sep 2010 12:34:38 -0400
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 20 Sep 2010 09:35:59 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <294372958.20100914171732@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <294372958.20100914171732@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
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:
>     [<ffffffff815bd155>] kmemleak_alloc+0x21/0x44
>     [<ffffffff8111a046>] __kmalloc+0x1c1/0x1ea
>     [<ffffffff81056dbf>] kzalloc_node+0xf/0x11
>     [<ffffffff8105741a>] get_one_free_irq_cfg+0x1a/0x45
>     [<ffffffff8105754e>] arch_init_chip_data+0x1a/0x39
>     [<ffffffff815bcb63>] irq_to_desc_alloc_node+0x18d/0x1b7
>     [<ffffffff81299cb8>] xen_allocate_pirq+0x99/0x185
>     [<ffffffff8103bef3>] xen_register_pirq+0x3e/0x98
>     [<ffffffff8103bf8f>] xen_register_gsi+0x42/0xb3
>     [<ffffffff810535bd>] acpi_register_gsi+0x22/0x5f
>     [<ffffffff812699ed>] acpi_pci_irq_enable+0x11f/0x212
>     [<ffffffff8149ddf4>] pcibios_enable_device+0x29/0x2d
>     [<ffffffff81243dbe>] do_pci_enable_device+0x28/0x40
>     [<ffffffff81243e2b>] __pci_enable_device_flags+0x55/0x70
>     [<ffffffff81243e54>] pci_enable_device+0xe/0x10
>     [<ffffffff812401f3>] pci_enable_bridges+0x2a/0x4e

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>