aboutsummaryrefslogtreecommitdiff
path: root/include/asm-x86/mach-visws/entry_arch.h
diff options
context:
space:
mode:
authorJesper Juhl <jesper.juhl@gmail.com>2008-03-28 14:16:12 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2008-03-28 14:45:23 -0700
commitd478376cb0dc9ab16a2b6e02fd8cd1174e724c64 (patch)
treefda590df6ece65517db78c3434898640f56c60ee /include/asm-x86/mach-visws/entry_arch.h
parent4cdc1d1fa5c5ac14dc21be19832f02fd0b83867e (diff)
driver core: fix small mem leak in driver_add_kobj()
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@gmail.com> Cc: Greg KH <greg@kroah.com> Cc: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/asm-x86/mach-visws/entry_arch.h')
0 files changed, 0 insertions, 0 deletions