From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: Memory leak on acpi_add_single_object()
Date: Fri, 4 Sep 2009 17:15:47 -0700 [thread overview]
Message-ID: <43e72e890909041715p203a06a8h7e836ecffdfc2eaa@mail.gmail.com> (raw)
In-Reply-To: <43e72e890909041534v4a4ec6ecpc6198be37adcfdef@mail.gmail.com>
On Fri, Sep 4, 2009 at 3:34 PM, Luis R. Rodriguez<mcgrof@gmail.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
prev parent reply other threads:[~2009-09-05 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 22:34 Luis R. Rodriguez
2009-09-05 0:15 ` Luis R. Rodriguez [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=43e72e890909041715p203a06a8h7e836ecffdfc2eaa@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®