From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pci-passthrough: suspected kmemleaks
Date: Mon, 20 Sep 2010 12:34:38 -0400 [thread overview]
Message-ID: <20100920163438.GD15129@dumpdata.com> (raw)
In-Reply-To: <294372958.20100914171732@eikelenboom.it>
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
prev parent reply other threads:[~2010-09-20 16:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 15:17 pci-passthrough: suspected kmemleaks Sander Eikelenboom
2010-09-20 16:34 ` Konrad Rzeszutek Wilk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100920163438.GD15129@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.