[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1248419547-30261-1-git-send-email-dfeng@redhat.com>
Date: Fri, 24 Jul 2009 15:12:27 +0800
From: Xiaotian Feng <dfeng@...hat.com>
To: gregkh@...e.de, linux-kernel@...r.kernel.org
Cc: Xiaotian Feng <dfeng@...hat.com>
Subject: [PATCH] lib/kobject: put kobject if kobject_add_internal fails
The proper way to use kobject_init_and_add should be:
retval = kobject_init_and_add(&foo->kobj, &foo_ktype, NULL, "%s", name);
if (retval) {
kobject_put(&foo->kobj); (*)
return NULL;
}
kobject_init_and_add calls kobject_add_vargs finally, kobject_add_vargs is divided
into two parts: kobject_set_name_vargs and kobject_add_internal. Both the two parts
may return an error. If the error is came from kobject_add_internal, this means
kobject_set_name_vargs already alloc memory for kobj->name.
So if caller forgets to use kobject_put when this kind of error occurs, the memory
for kobj->name leaks. Unfortunately, most of the callers is forgotten to use
kobject_put in this rare situation, grep kobject_init_and_add in kernel source code,
there are 20+ files forgotten this. So I'd prefer to fix this in lib/kobject, not
the whole 20+ files.
Signed-off-by: Xiaotian Feng <dfeng@...hat.com>
---
lib/kobject.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lib/kobject.c b/lib/kobject.c
index b512b74..e6e6e03 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -200,6 +200,7 @@ static int kobject_add_internal(struct kobject *kobj)
printk(KERN_ERR "%s failed for %s (%d)\n",
__func__, kobject_name(kobj), error);
dump_stack();
+ kobject_put(kobj);
} else
kobj->state_in_sysfs = 1;
@@ -657,7 +658,6 @@ struct kobject *kobject_create_and_add(const char *name, struct kobject *parent)
if (retval) {
printk(KERN_WARNING "%s: kobject_add error: %d\n",
__func__, retval);
- kobject_put(kobj);
kobj = NULL;
}
return kobj;
--
1.6.2.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists