Skip to contentSkip to conversation

Memory leak on acpi_add_single_object()

DISCUSSION Luis R. Rodriguez 1 participant 2 messages Sep 4, 2009 – Sep 5, 2009 ACPI

lore
Share & tools
lore
#0 lore raw

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

Luis

#1 lore raw
Quoted 53 lines · Luis R. Rodriguez

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
Quoted 1 line

   [<ffffffffffffffff>] 0xffffffffffffffff

I get these even after issuing manual scans.

Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html