[<prev] [next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.1.00.0803212309520.10052@dragon.funnycrock.com>
Date: Fri, 21 Mar 2008 23:16:46 +0100 (CET)
From: Jesper Juhl <jesper.juhl@...il.com>
To: Greg Kroah-Hartman <gregkh@...e.de>
cc: Patrick Mochel <mochel@...l.org>,
Patrick Mochel <mochelp@...inity.powertie.org>,
LKML <linux-kernel@...r.kernel.org>,
Jesper Juhl <jesper.juhl@...il.com>
Subject: [PATCH][RFC] fix small mem leak in driver_add_kobj()
Hi,
The Coverity checker spotted that we leak the storage allocated to 'name'
in int driver_add_kobj().
The leak looks legit to me - this is the code :
int driver_add_kobj(struct device_driver *drv, struct kobject *kobj,
const char *fmt, ...)
{
va_list args;
char *name;
int ret;
va_start(args, fmt);
name = kvasprintf(GFP_KERNEL, fmt, args);
^^^^^^^^ This dynamically allocates space...
va_end(args);
if (!name)
return -ENOMEM;
return kobject_add(kobj, &drv->p->kobj, "%s", name);
^^^^^^^^ This neglects to free the space allocated
}
Inside kobject_add() a copy of 'name' will be made and used.
As far as I can see, Coverity is correct in flagging this as a leak, but
I'd like some configmation before the patch is applied.
This should fix it :
Signed-off-by: Jesper Juhl <jesper.juhl@...il.com>
---
driver.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/base/driver.c b/drivers/base/driver.c
index bf31a01..9a6537f 100644
--- a/drivers/base/driver.c
+++ b/drivers/base/driver.c
@@ -133,6 +133,7 @@ int driver_add_kobj(struct device_driver *drv, struct kobject *kobj,
{
va_list args;
char *name;
+ int ret;
va_start(args, fmt);
name = kvasprintf(GFP_KERNEL, fmt, args);
@@ -141,7 +142,9 @@ int driver_add_kobj(struct device_driver *drv, struct kobject *kobj,
if (!name)
return -ENOMEM;
- return kobject_add(kobj, &drv->p->kobj, "%s", name);
+ ret = kobject_add(kobj, &drv->p->kobj, "%s", name);
+ kfree(name);
+ return ret;
}
EXPORT_SYMBOL_GPL(driver_add_kobj);
--
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