Re: Memory leak on acpi_add_single_object()

[Luis R. Rodriguez]

On Fri, Sep 4, 2009 at 3:34 PM, Luis R. Rodriguez<mcgrof@xxxxxxxxx> wrote:
> Here are 3 acpi_add_single_object() kmemleak reports on 2.6.31-rc8 +
> Catalin's kmemleak tree (git://linux-arm.org/linux-2.6 master).
>
> unreferenced object 0xffff88003c405940 (size 64):
> Âcomm "swapper", pid 1, jiffies 4294892466
> Âhex dump (first 32 bytes):
> Â Â00 00 00 00 38 00 00 00 00 00 00 00 00 00 00 00 Â....8...........
> Â Â00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Â................
> Âbacktrace:
> Â Â[<ffffffff814e9d55>] kmemleak_alloc+0x25/0x60
> Â Â[<ffffffff81119fbb>] __kmalloc+0x16b/0x250
> Â Â[<ffffffff812bb379>] kzalloc+0xf/0x11
> Â Â[<ffffffff812bb983>] acpi_add_single_object+0x58e/0xd3c
> Â Â[<ffffffff812bc34c>] acpi_bus_scan+0x125/0x1af
> Â Â[<ffffffff81818842>] acpi_scan_init+0xc8/0xe9
> Â Â[<ffffffff818185fd>] acpi_init+0x21f/0x265
> Â Â[<ffffffff8100a047>] do_one_initcall+0x37/0x1a0
> Â Â[<ffffffff817efa16>] kernel_init+0x164/0x1ba
> Â Â[<ffffffff810130ca>] child_rip+0xa/0x20
> Â Â[<ffffffffffffffff>] 0xffffffffffffffff
> unreferenced object 0xffff88003c405980 (size 64):
> Âcomm "swapper", pid 1, jiffies 4294892467
> Âhex dump (first 32 bytes):
> Â Â00 00 00 00 38 00 00 00 00 00 00 00 00 00 00 00 Â....8...........
> Â Â00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Â................
> Âbacktrace:
> Â Â[<ffffffff814e9d55>] kmemleak_alloc+0x25/0x60
> Â Â[<ffffffff81119fbb>] __kmalloc+0x16b/0x250
> Â Â[<ffffffff812bb379>] kzalloc+0xf/0x11
> Â Â[<ffffffff812bb983>] acpi_add_single_object+0x58e/0xd3c
> Â Â[<ffffffff812bc34c>] acpi_bus_scan+0x125/0x1af
> Â Â[<ffffffff81818842>] acpi_scan_init+0xc8/0xe9
> Â Â[<ffffffff818185fd>] acpi_init+0x21f/0x265
> Â Â[<ffffffff8100a047>] do_one_initcall+0x37/0x1a0
> Â Â[<ffffffff817efa16>] kernel_init+0x164/0x1ba
> Â Â[<ffffffff810130ca>] child_rip+0xa/0x20
> Â Â[<ffffffffffffffff>] 0xffffffffffffffff
> unreferenced object 0xffff88003c4059c0 (size 64):
> Âcomm "swapper", pid 1, jiffies 4294892470
> Âhex dump (first 32 bytes):
> Â Â00 00 00 00 38 00 00 00 00 00 00 00 00 00 00 00 Â....8...........
> Â Â00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Â................
> Âbacktrace:
> Â Â[<ffffffff814e9d55>] kmemleak_alloc+0x25/0x60
> Â Â[<ffffffff81119fbb>] __kmalloc+0x16b/0x250
> Â Â[<ffffffff812bb379>] kzalloc+0xf/0x11
> Â Â[<ffffffff812bb983>] acpi_add_single_object+0x58e/0xd3c
> Â Â[<ffffffff812bc34c>] acpi_bus_scan+0x125/0x1af
> Â Â[<ffffffff81818842>] acpi_scan_init+0xc8/0xe9
> Â Â[<ffffffff818185fd>] acpi_init+0x21f/0x265
> Â Â[<ffffffff8100a047>] do_one_initcall+0x37/0x1a0
> Â Â[<ffffffff817efa16>] kernel_init+0x164/0x1ba
> Â Â[<ffffffff810130ca>] child_rip+0xa/0x20
> Â Â[<ffffffffffffffff>] 0xffffffffffffffff

I get these even after issuing manual scans.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/