From: Julia Lawall <julia@diku.dk>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 1/8] arch/mips/txx9: introduce missing kfree, iounmap
Date: Sun, 13 Sep 2009 17:49:40 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0909131749150.25903@ask.diku.dk> (raw)
In-Reply-To: <20090914.003321.160496287.anemo@mba.ocn.ne.jp>
On Mon, 14 Sep 2009, Atsushi Nemoto wrote:
> On Sun, 13 Sep 2009 17:14:06 +0200 (CEST), Julia Lawall <julia@diku.dk> wrote:
> > > This patch add some correctness, but obviously incomplete: there are
> > > more error pathes without iounmap/kfree/etc. in this function.
> >
> > The only other error path that I see is:
> >
> > pdev = platform_device_alloc("leds-gpio", basenum);
> > if (!pdev)
> > return;
> >
> > But at that point the call gpiochip_add(&iocled->chip) has already
> > succeeded. From looking at this function, I have the impression that it
> > makes the iocled structure available from a global array, gpio_desc.
> > Since the function containing the above code doesn't return any error
> > code, perhaps the caller will not know whether this platform_device_alloc
> > error occurred or not. There would also be at least the problem of
> > getting the pointer out of the gpio_desc structure. I guess this could be
> > done with gpiochip_remove?
> >
> > I can certainly make a new patch using the goto style, but let me know
> > what to do about the above issue.
>
> Yes, this gpiochip is only used by leds-gpio driver. So
> gpiochip_remove() would be the right thing to do when something
> failed.
>
> Also there is one another error path: platform_device_add() failure at
> the end of this function.
OK, I see. I will submit an improved patch. Thanks for the explanations.
julia
next prev parent reply other threads:[~2009-09-13 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 16:21 [PATCH 1/8] arch/mips/txx9: introduce missing kfree, iounmap Julia Lawall
2009-09-13 14:25 ` Atsushi Nemoto
2009-09-13 15:14 ` Julia Lawall
2009-09-13 15:33 ` Atsushi Nemoto
2009-09-13 15:49 ` Julia Lawall [this message]
2009-09-13 19:15 ` Julia Lawall
2009-09-14 14:56 ` Ralf Baechle
2009-09-15 5:03 ` Julia Lawall
2009-09-15 15:45 ` Atsushi Nemoto
2009-09-15 15:47 ` Julia Lawall
2009-09-15 15:56 ` Julia Lawall
2009-09-15 14:02 ` Ralf Rösch
2009-09-15 14:35 ` Julia Lawall
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=Pine.LNX.4.64.0909131749150.25903@ask.diku.dk \
--to=julia@diku.dk \
--cc=anemo@mba.ocn.ne.jp \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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