linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Syam Sidhardhan <syamsidhardh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Igor Grinberg <grinberg-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org,
	ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org
Subject: Re: [PATCH 07/59] i2c/i2c-pxa: Fix possible NULL pointer dereference
Date: Mon, 25 Feb 2013 20:24:39 +0530	[thread overview]
Message-ID: <CAFBvHidGRezNmPYg2BEji5nfK-+g7TWhUfWL1UY9rVqxHmUunw@mail.gmail.com> (raw)
In-Reply-To: <512B245A.1020703-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>

Hi Igor,

On Mon, Feb 25, 2013 at 2:14 PM, Igor Grinberg <grinberg-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org> wrote:
> On 02/25/13 00:44, Syam Sidhardhan wrote:
>> When platform_get_resource() returns NULL, there is a possible
>> NULL pointer dereference in release_mem_region(). Rearrange the
>> goto lables appropriately.
>>
>> Signed-off-by: Syam Sidhardhan <s.syam-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
>
> I think this has been already addressed in [1],
> but I don't know if it was applied already...
>
> [1] https://patchwork.kernel.org/patch/2141301/
>
>> ---
>>
>> Only compile tested.
>>
>>  drivers/i2c/busses/i2c-pxa.c |   10 +++++-----
>>  1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-pxa.c b/drivers/i2c/busses/i2c-pxa.c
>> index 1034d93..7ddda5c 100644
>> --- a/drivers/i2c/busses/i2c-pxa.c
>> +++ b/drivers/i2c/busses/i2c-pxa.c
>> @@ -1104,18 +1104,18 @@ static int i2c_pxa_probe(struct platform_device *dev)
>>       if (ret > 0)
>>               ret = i2c_pxa_probe_pdata(dev, i2c, &i2c_type);
>>       if (ret < 0)
>> -             goto eclk;
>> +             goto emalloc;
>>
>>       res = platform_get_resource(dev, IORESOURCE_MEM, 0);
>>       irq = platform_get_irq(dev, 0);
>>       if (res == NULL || irq < 0) {
>>               ret = -ENODEV;
>> -             goto eclk;
>> +             goto emalloc;
>>       }
>>
>>       if (!request_mem_region(res->start, resource_size(res), res->name)) {
>>               ret = -ENOMEM;
>> -             goto eclk;
>> +             goto emalloc;
>>       }
>>
>>       i2c->adap.owner   = THIS_MODULE;
>> @@ -1209,9 +1209,9 @@ ereqirq:
>>  eremap:
>>       clk_put(i2c->clk);
>>  eclk:
>> -     kfree(i2c);
>> -emalloc:
>>       release_mem_region(res->start, resource_size(res));
>> +emalloc:
>> +     kfree(i2c);
>>       return ret;
>>  }
>>

You are correct. It has been already posted by Cong Ding.
Kindly ignore this patch.

Thanks,
Syam

      parent reply	other threads:[~2013-02-25 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-24 22:44 [PATCH 07/59] i2c/i2c-pxa: Fix possible NULL pointer dereference Syam Sidhardhan
     [not found] ` <1361745852-28629-1-git-send-email-s.syam-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-02-25  8:44   ` Igor Grinberg
     [not found]     ` <512B245A.1020703-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2013-02-25 14:54       ` Syam Sidhardhan [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=CAFBvHidGRezNmPYg2BEji5nfK-+g7TWhUfWL1UY9rVqxHmUunw@mail.gmail.com \
    --to=syamsidhardh-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=grinberg-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.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;
as well as URLs for NNTP newsgroup(s).