From: Artem Bityutskiy <dedekind1@gmail.com>
To: linux-omap@vger.kernel.org
Cc: Nishanth Menon <nm@ti.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
Thara Gopinath <thara@ti.com>,
Peter p2 De Schrijver <peter.de-schrijver@nokia.com>
Subject: Re: [PATCH 1/2] omap3: sr: fix memory leak and simplify the code
Date: Fri, 09 Jul 2010 16:22:47 +0300 [thread overview]
Message-ID: <1278681767.9953.113.camel@localhost> (raw)
In-Reply-To: <1278681612-10521-1-git-send-email-dedekind1@gmail.com>
On Fri, 2010-07-09 at 16:20 +0300, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
>
> This patch fixes the following problem indicated by kmemleak:
>
> kmemleak: unreferenced object 0xdf93c280 (size 64):
> kmemleak: backtrace:
> kmemleak: [<c00df6d4>] create_object+0x104/0x200
> kmemleak: [<c00d7638>] kmem_cache_alloc+0xe4/0xf4
> kmemleak: [<c000fc38>] omap_devinit_smartreflex+0x44/0x244
> kmemleak: [<c003a33c>] do_one_initcall+0x5c/0x1b8
> kmemleak: [<c00083fc>] kernel_init+0x94/0x110
> kmemleak: [<c003ba04>] kernel_thread_exit+0x0/0x8
>
> The reason is that 'omap_devinit_smartreflex()' allocates 'sr_data',
> then passes it to 'omap_device_build()', which 'kmemdup()'s it and
> uses the copy. But 'omap_devinit_smartreflex()' never frees 'sr_data'.
>
> This patch make 'sr_data' to be a stack variable, which eliminates
> the memory leak and simplifies the code a bit.
>
> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> ---
> arch/arm/mach-omap2/sr_device.c | 27 +++++++++------------------
> 1 files changed, 9 insertions(+), 18 deletions(-)
Note, I only compile-tested both of the patches, so be careful.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-07-09 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 13:20 [PATCH 1/2] omap3: sr: fix memory leak and simplify the code Artem Bityutskiy
2010-07-09 13:20 ` [PATCH 2/2] omap3: sr: improve errors handling Artem Bityutskiy
2010-07-09 15:02 ` Nishanth Menon
2010-07-09 15:05 ` Gopinath, Thara
2010-07-09 15:44 ` Artem Bityutskiy
2010-07-09 15:51 ` Nishanth Menon
2010-07-09 15:50 ` Artem Bityutskiy
2010-07-09 16:00 ` Menon, Nishanth
2010-07-09 16:02 ` Artem Bityutskiy
2010-07-12 13:36 ` Artem Bityutskiy
2010-07-09 13:22 ` Artem Bityutskiy [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=1278681767.9953.113.camel@localhost \
--to=dedekind1@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.de-schrijver@nokia.com \
--cc=thara@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.