From: WANG Cong <xiyou.wangcong@gmail.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
viro@zeniv.linux.org.uk
Subject: Re: [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc.
Date: Thu, 5 Apr 2007 22:44:09 +0800 [thread overview]
Message-ID: <20070405144409.GA5294@localhost.localdomain> (raw)
In-Reply-To: <20070405111142.4723035f@gondolin.boeblingen.de.ibm.com>
On Thu, Apr 05, 2007 at 11:11:42AM +0200, Cornelia Huck wrote:
>On Thu, 5 Apr 2007 12:54:11 +0800,
>WANG Cong <xiyou.wangcong@gmail.com> wrote:
>
>> --- linux-2.6.21-rc5-mm3/fs/partitions/check.c.orig 2007-03-30 21:35:45.000000000 +0800
>> +++ linux-2.6.21-rc5-mm3/fs/partitions/check.c 2007-04-02 21:29:02.000000000 +0800
>> @@ -385,10 +385,18 @@ void add_partition(struct gendisk *disk,
>> p->kobj.parent = &disk->kobj;
>> p->kobj.ktype = &ktype_part;
>> kobject_init(&p->kobj);
>> - kobject_add(&p->kobj);
>> + if (kobject_add(&p->kobj)) {
>> + kfree(p);
>> + return;
>> + }
>> if (!disk->part_uevent_suppress)
>> kobject_uevent(&p->kobj, KOBJ_ADD);
>> - sysfs_create_link(&p->kobj, &block_subsys.kset.kobj, "subsystem");
>> + if (sysfs_create_link(&p->kobj, &block_subsys.kset.kobj, "subsystem")) {
>> + kobject_uevent(&p->kobj, KOBJ_REMOVE);
>> + kobject_del(&p->kobj);
>> + kfree(p);
>
>You should use kobject_put instead of kfree, since someone could have
>(theoretically) obtained a reference on the object after the
>kobject_add. (Or just use kobject_unregister, if the delete uevent
>isn't suppressed anyway.)
>
I can't understand that. The memory pointed by 'p' is obtained via kmalloc(), _not_ kobject_get. How can we use kobject_put instead?
Thanks!
next prev parent reply other threads:[~2007-04-05 14:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 7:32 [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc Cong WANG
2007-04-02 11:01 ` Cornelia Huck
2007-04-05 4:54 ` WANG Cong
2007-04-05 9:11 ` Cornelia Huck
2007-04-05 14:44 ` WANG Cong [this message]
2007-04-05 15:05 ` Cornelia Huck
2007-04-05 15:27 ` WANG Cong
2007-04-05 16:00 ` Cornelia Huck
2007-04-06 2:53 ` WANG Cong
2007-04-10 12:31 ` Cornelia Huck
2007-04-10 12:35 ` [Patch -mm] kobject: kobject_add() reference leak Cornelia Huck
2007-04-10 14:08 ` [-mm3 PATCH] (Retry) Check the return value of kobject_add and etc WANG Cong
2007-04-10 22:18 ` Andrew Morton
2007-04-11 6:45 ` WANG Cong
2007-04-11 7:19 ` Andrew Morton
2007-04-11 9:24 ` Cornelia Huck
-- strict thread matches above, loose matches on Subject: below --
2007-04-01 8:22 Parag Warudkar
2007-04-01 13:46 ` Parag Warudkar
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=20070405144409.GA5294@localhost.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cornelia.huck@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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