From: vimal singh <vimal.newwork@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Stoyan Gaydarov <sgayda2@uiuc.edu>,
linux-kernel@vger.kernel.org, David.Woodhouse@intel.com,
sr@denx.de, kay.sievers@vrfy.org, gregkh@suse.de,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [mtd] fixed faulty check
Date: Thu, 30 Jul 2009 19:09:09 +0530 [thread overview]
Message-ID: <ce9ab5790907300639k3173446csbd07198055bfe122@mail.gmail.com> (raw)
In-Reply-To: <4A719A27.8050509@linutronix.de>
On Thu, Jul 30, 2009 at 6:33 PM, Sebastian Andrzej
Siewior<bigeasy@linutronix.de> wrote:
> Stoyan Gaydarov wrote:
>>
>> Resubmit of a patch with some additions, see
>> http://lkml.org/lkml/2009/7/30/97
>>
> Please add a description of the path here. That's the place where people
> are looking for them. The link might be a an additional reference.
>
>> Signed-off-by: Stoyan Gaydarov <sgayda2@uiuc.edu>
>> ---
>> drivers/mtd/maps/physmap_of.c | 3 ++-
>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/mtd/maps/physmap_of.c b/drivers/mtd/maps/physmap_of.c
>> index 39d357b..e7ab5f0 100644
>> --- a/drivers/mtd/maps/physmap_of.c
>> +++ b/drivers/mtd/maps/physmap_of.c
>> @@ -215,7 +215,8 @@ static int __devinit of_flash_probe(struct of_device
>> *dev,
>> goto err_out;
>> mtd_list = kzalloc(sizeof(struct mtd_info) * count, GFP_KERNEL);
>> - if (!info)
>> + if (!mtd_list)
>> + kfree(info);
>> goto err_out;
What if you go to 'err_out' due to some other error?? Do not you need
to free 'info'?
So, better free it in at the label.
Currently label is like below, which is again incorrect.
-----code snippet (line 339)-----
err_out:
kfree(mtd_list);
of_flash_remove(dev);
-------------------------------------------
Think about when you get jump to this label even before 'mtd_list' is
allocated. This is the scenario of null pointer dereferencing.
So, this requires two separate labels:
-one label for errors which occur before 'mtd_list' memory allocation
-and, another for then onward errors
something like below:
err_out2:
kfree(info);
kfree(mtd_list);
err_out1:
of_flash_remove(dev);
-vimal
>
> This is not python, you have to be explicit about braces. Now your code
> looks like this:
>
> mtd_list = kzalloc(sizeof(struct mtd_info) * count, GFP_KERNEL);
> if (!mtd_list)
> kfree(info);
> goto err_out;
>>
>> dev_set_drvdata(&dev->dev, info);
>
>
> Sebastian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
---
Regards,
\/ | |\/| /-\ |_
____ __o
------ -\<,
----- ( )/ ( )
next prev parent reply other threads:[~2009-07-30 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 12:49 Stoyan Gaydarov
2009-07-30 13:03 ` Sebastian Andrzej Siewior
2009-07-30 13:39 ` vimal singh [this message]
2009-07-30 13:47 ` Sebastian Andrzej Siewior
2009-07-30 14:14 ` vimal singh
[not found] ` <4A71AD5E.4080704@uiuc.edu>
2009-07-30 14:34 ` vimal singh
2009-07-30 14:53 ` Sebastian Andrzej Siewior
2009-07-30 15:13 ` vimal singh
[not found] ` <4A71B940.80607@uiuc.edu>
2009-07-30 15:24 ` vimal singh
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=ce9ab5790907300639k3173446csbd07198055bfe122@mail.gmail.com \
--to=vimal.newwork@gmail.com \
--cc=David.Woodhouse@intel.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sgayda2@uiuc.edu \
--cc=sr@denx.de \
/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®