All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <gg@slimlogic.co.uk>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>
Subject: Re: [PATCH] mfd: Don't leak init_data in tps65910_i2c_probe
Date: Tue, 05 Jul 2011 23:54:55 +0100	[thread overview]
Message-ID: <4E13963F.1050905@slimlogic.co.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.1107060027280.9158@swampdragon.chaosbits.net>

On 07/05/2011 11:29 PM, Jesper Juhl wrote:
> On Tue, 5 Jul 2011, Jesper Juhl wrote:
>
>> On Mon, 4 Jul 2011, Samuel Ortiz wrote:
>>
> [...]
>>> This is not a memory leak fix. And I actually prefer the == NULL check.
>>> Please remove the == NULL check replacement with !* and keep only the memory
>>> leak fixing part.
>>>
> Here's an updated patch.
>
>
> From: Jesper Juhl <jj@chaosbits.net>
> Subject: [PATCH] mfd: Don't leak init_data in tps65910_i2c_probe
>
> There are a couple of situations where we leak init_data in
> drivers/mfd/tps65910.c:tps65910_i2c_probe() - this patch should take
> care of them.
>
> Signed-off-by: Jesper Juhl <jj@chaosbits.net>
> ---
>  drivers/mfd/tps65910.c |    6 +++++-
>  1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mfd/tps65910.c b/drivers/mfd/tps65910.c
> index 2229e66..7a3eb2d 100644
> --- a/drivers/mfd/tps65910.c
> +++ b/drivers/mfd/tps65910.c
> @@ -151,8 +151,10 @@ static int tps65910_i2c_probe(struct i2c_client *i2c,
>  	init_data->irq_base = pmic_plat_data->irq;
>  
>  	tps65910 = kzalloc(sizeof(struct tps65910), GFP_KERNEL);
> -	if (tps65910 == NULL)
> +	if (tps65910 == NULL) {
> +		kfree(init_data);
>  		return -ENOMEM;
> +	}
>  
>  	i2c_set_clientdata(i2c, tps65910);
>  	tps65910->dev = &i2c->dev;
> @@ -174,11 +176,13 @@ static int tps65910_i2c_probe(struct i2c_client *i2c,
>  	if (ret < 0)
>  		goto err;
>  
> +	kfree(init_data);
>  	return ret;
>  
>  err:
>  	mfd_remove_devices(tps65910->dev);
>  	kfree(tps65910);
> +	kfree(init_data);
>  	return ret;
>  }
>  
Sorry didnt reply to this first time round.

Acked-by: Graeme Gregory <gg@slimlogic.co.uk>


  reply	other threads:[~2011-07-05 22:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-02 19:21 [PATCH] mfd: Don't leak init_data in tps65910_i2c_probe Jesper Juhl
2011-07-04 17:33 ` Samuel Ortiz
2011-07-05  7:46   ` Jesper Juhl
2011-07-05 22:29     ` Jesper Juhl
2011-07-05 22:54       ` Graeme Gregory [this message]
2011-07-06 18:34       ` Samuel Ortiz

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=4E13963F.1050905@slimlogic.co.uk \
    --to=gg@slimlogic.co.uk \
    --cc=jedu@slimlogic.co.uk \
    --cc=jj@chaosbits.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.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.