From: David Brownell <david-b@pacbell.net>
To: lrg@slimlogic.co.uk, broonie@opensource.wolfsonmicro.com
Cc: Paul Walmsley <paul@pwsan.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] regulator core: fix double-free in regulator_register() error path
Date: Sat, 25 Apr 2009 15:11:56 -0700 [thread overview]
Message-ID: <200904251511.57390.david-b@pacbell.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0904250526210.28378@utopia.booyaka.com>
On Saturday 25 April 2009, Paul Walmsley wrote:
>
> During regulator registration, any error after device_register() will
> cause a double-free on the struct regulator_dev 'rdev'. The bug is in
> drivers/regulator/core.c:regulator_register():
>
> ...
> scrub:
> device_unregister(&rdev->dev);
> clean:
> kfree(rdev); <---
> rdev = ERR_PTR(ret);
> goto out;
> ...
>
> device_unregister() calls regulator_dev_release() which frees rdev. The
> subsequent kfree corrupts memory and causes some OMAP3 systems to oops on
> boot in regulator_get().
>
> Applies against 2.6.30-rc3.
>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
This looks like it would address the oopsing I mentioned a
while back, since affects cleanup paths after errors during
driver probe().
> ---
> drivers/regulator/core.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> index 01f7702..fabd2e0 100644
> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@ -2080,6 +2080,10 @@ out:
>
> scrub:
> device_unregister(&rdev->dev);
> + /* device core frees rdev */
> + rdev = ERR_PTR(ret);
> + goto out;
> +
> clean:
> kfree(rdev);
> rdev = ERR_PTR(ret);
> --
> 1.6.3.rc1.51.gea0b7
>
>
next prev parent reply other threads:[~2009-04-25 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-25 11:28 [PATCH] regulator core: fix double-free in regulator_register() error path Paul Walmsley
2009-04-25 22:11 ` David Brownell [this message]
2009-04-26 4:53 ` Paul Walmsley
2009-04-28 3:08 ` David Brownell
2009-04-28 8:16 ` Mark Brown
2009-04-28 9:32 ` David Brownell
2009-04-28 11:00 ` Mark Brown
2009-04-28 11:47 ` David Brownell
2009-04-28 12:47 ` Mark Brown
2009-04-26 9:23 ` Mark Brown
2009-04-27 11:40 ` Liam Girdwood
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=200904251511.57390.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=paul@pwsan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox