From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: catalin.marinas@gmail.com
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2.6.17-rc6] Fix the memory leak in acpi_evaluate_integer()
Date: Wed, 7 Jun 2006 14:15:24 +0200 [thread overview]
Message-ID: <6bffcb0e0606070515j797d6cb2o66d055947550d48b@mail.gmail.com> (raw)
In-Reply-To: <20060607113354.9720.85323.stgit@localhost.localdomain>
Hi Catalin,
On 07/06/06, Catalin Marinas <catalin.marinas@arm.com> wrote:
> From: Catalin Marinas <catalin.marinas@arm.com>
>
> A leak can happen because of the early returns from this function
> (discovered by kmemleak).
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> ---
all
orphan pointer 0xf7e97654 (size 40):
c0151044: <kmem_cache_alloc>
c01e8656: <acpi_os_acquire_object>
c01fe087: <acpi_ut_allocate_object_desc_dbg>
c01fdf1b: <acpi_ut_create_internal_object_dbg>
c01ec2a0: <acpi_ev_execute_reg_method>
c01ec898: <acpi_ev_reg_run>
c01f7453: <acpi_ns_walk_namespace>
c01ec859: <acpi_ev_execute_reg_methods>
are gone. But now I get a lot of
orphan pointer 0xf7ea1654 (size 40):
c015208c: <kmem_cache_alloc>
c01eb6c2: <acpi_os_acquire_object>
c02010f7: <acpi_ut_allocate_object_desc_dbg>
c0200f8b: <acpi_ut_create_internal_object_dbg>
c01ef310: <acpi_ev_execute_reg_method>
c01ef908: <acpi_ev_reg_run>
c01fa4c3: <acpi_ns_walk_namespace>
c01ef8c9: <acpi_ev_execute_reg_methods>
c01ef293: <acpi_ev_initialize_op_regions>
c02000d4: <acpi_initialize_objects>
c03a0a37: <acpi_bus_init>
c03a0ada: <acpi_init>
c038e871: <do_initcalls>
c038e91e: <do_basic_setup>
c0100367: <init>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
next prev parent reply other threads:[~2006-06-07 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 11:33 [PATCH 2.6.17-rc6] Fix the memory leak in acpi_evaluate_integer() Catalin Marinas
2006-06-07 12:15 ` Michal Piotrowski [this message]
2006-06-07 12:17 ` Michal Piotrowski
2006-06-07 12:37 ` Catalin Marinas
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=6bffcb0e0606070515j797d6cb2o66d055947550d48b@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=catalin.marinas@gmail.com \
--cc=linux-acpi@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