mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@mail.by>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@mail.by>,
	Greg KH <gregkh@suse.de>, Kay Sievers <kay.sievers@vrfy.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kobject_set_name_vargs memory leak
Date: Sat, 27 Jun 2009 02:14:50 +0300	[thread overview]
Message-ID: <20090626231450.GC3858@localdomain.by> (raw)
In-Reply-To: <m17hyyfvnv.fsf@fess.ebiederm.org>

On (06/26/09 16:00), Eric W. Biederman wrote:
> >> > Fix memory leak when kobject_set_name_vargs returns -ENOMEM.
> >> > 
> >> > Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@mail.by>
> >> > ---
> >> > diff --git a/lib/kobject.c b/lib/kobject.c
> >> > index b512b74..922cd8c 100644
> >> > --- a/lib/kobject.c
> >> > +++ b/lib/kobject.c
> >> > @@ -222,8 +222,10 @@ int kobject_set_name_vargs(struct kobject *kobj, const char *fmt,
> >> >  		return 0;
> >> >  
> >> >  	kobj->name = kvasprintf(GFP_KERNEL, fmt, vargs);
> >> > -	if (!kobj->name)
> >> > +	if (!kobj->name) {
> >> > +		kfree(old_name);
> >> >  		return -ENOMEM;
> >> > +	}
> >> 
> >> 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.
> >> 
> > Hello Greg,
> >
> > int kobject_set_name_vargs.... {
> > 	const char *old_name = kobj->name;
> >
> > old_name is local variable.
> >
> > In the following lines we overwrite kobject->name.
> >
> > 	kobj->name = kvasprintf(GFP_KERNEL, fmt, vargs);
> > 	if (!kobj->name)
> > 		return -ENOMEM;
> >
> > It's not clear to me how we can do anything (including kfree) with old_name after 'return -ENOMEM'.
> 
> My feel is that if we fail we should restore kobject->name to old_name.
> 
> That should also prevent the leak without getting us into trouble elsewhere.
> 
> Eric
> 
Or work with 'new_name' and overwrite kobject->name only 'if(new_name)'.
I thought about restoring. ( Blue or Red Pill? :) )

diff --git a/lib/kobject.c b/lib/kobject.c
index b512b74..d6b1502 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -222,8 +222,10 @@ int kobject_set_name_vargs(struct kobject *kobj, const char *fmt,
 		return 0;
 
 	kobj->name = kvasprintf(GFP_KERNEL, fmt, vargs);
-	if (!kobj->name)
+	if (!kobj->name) {
+		kobj->name = old_name;
 		return -ENOMEM;
+	}
 
 	/* ewww... some of these buggers have '/' in the name ... */
 	while ((s = strchr(kobj->name, '/')))


	Sergey

  reply	other threads:[~2009-06-26 23:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 14:36 Sergey Senozhatsky
2009-06-26 14:49 ` Greg KH
2009-06-26 22:29   ` Sergey Senozhatsky
2009-06-26 23:00     ` Eric W. Biederman
2009-06-26 23:14       ` Sergey Senozhatsky [this message]
2009-06-26 23:23   ` Sergey Senozhatsky
2009-06-27  2:10     ` Eric W. Biederman
2009-06-27  9:33       ` Sergey Senozhatsky
2009-06-27  9:39       ` Sergey Senozhatsky
2009-06-27 23:56         ` Kay Sievers
2009-06-28 12:07           ` Eric W. Biederman
2009-06-28 13:02             ` Kay Sievers
2009-06-28 13:13               ` Eric W. Biederman
2009-06-28 13:40             ` Sergey Senozhatsky
2009-06-29  9:53             ` Dave Young

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=20090626231450.GC3858@localdomain.by \
    --to=sergey.senozhatsky@mail.by \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®