lkml.org 
[lkml]   [2009]   [Jun]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] kobject_set_name_vargs memory leak
On (06/26/09 07:49), Greg KH wrote:
> We've been through this before (search lkml archives). If kvasprintf
> fails, then we don't want to free old_name, as the caller might want to
> do something with it.
>
> Or something along those lines, I can't remember the exact reasoning
> this early in the morning.
>
> Kay, do you remember?
>
I found.
http://lkml.org/lkml/2009/5/11/11

>kobject with name set before should not come into this function,
>kobject_rename should be used instead.

It's just would be safer to kfree or restore I guess.

> thanks,
>
> greg k-h
>

Sergey


\
 
 \ /
  Last update: 2009-06-27 01:25    [W:0.070 / U:0.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site