linux-kernel - Re: Memory leak on acpi_add_single

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <43e72e890909041715p203a06a8h7e836ecffdfc2eaa@mail.gmail.com>
Date:	Fri, 4 Sep 2009 17:15:47 -0700
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Cc:	linux-kernel@...r.kernel.org,
	Catalin Marinas <catalin.marinas@....com>
Subject: Re: Memory leak on acpi_add_single_object()

On Fri, Sep 4, 2009 at 3:34 PM, Luis R. Rodriguez<mcgrof@...il.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/