From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] physmap: Fix leak of memory returned by parse_mtd_partitions
Date: Wed, 12 Nov 2008 11:08:00 -0500 [thread overview]
Message-ID: <8bd0f97a0811120808p5858d5adleeef43b1d374bee1@mail.gmail.com> (raw)
In-Reply-To: <20081113.005534.56563769.anemo@mba.ocn.ne.jp>
On Wed, Nov 12, 2008 at 10:55, Atsushi Nemoto wrote:
> On Wed, 12 Nov 2008 23:57:33 +0900 (JST), Atsushi Nemoto wrote:
>> The mtd partition parser returns an allocated pointer array of
>> mtd_partition. The caller must free it. The array is used only for
>> add_mtd_partitions(), so free it just after the call.
>>
>> Signed-off-by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
>> ---
>> drivers/mtd/maps/physmap.c | 17 ++++++++---------
>> 1 files changed, 8 insertions(+), 9 deletions(-)
>
> And many other callers of parse_mtd_partitions() also do not free the
> returned memory. With a quick look, 21 of 36 have same defect.
i wonder why we duplicate this same code block in so many places. and
why does every driver have to declare its own list of parsers ? cant
we unify all of these in one place ?
> drivers/mtd/maps/bfin-async-flash.c
i can fix this one if no one else gets to it
-mikex
next prev parent reply other threads:[~2008-11-12 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 14:57 Atsushi Nemoto
2008-11-12 15:28 ` Atsushi Nemoto
2008-11-12 15:55 ` Atsushi Nemoto
2008-11-12 16:08 ` Mike Frysinger [this message]
2008-11-18 13:57 ` David Woodhouse
2008-11-18 14:04 ` Artem Bityutskiy
2008-11-18 14:15 ` David Woodhouse
2009-02-24 13:35 ` Sascha Hauer
2009-02-24 14:36 ` Atsushi Nemoto
2009-02-24 15:29 ` Sascha Hauer
2009-02-25 1:31 ` Atsushi Nemoto
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=8bd0f97a0811120808p5858d5adleeef43b1d374bee1@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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®