All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Patrick Pannuto <ppannuto@codeaurora.org>
Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
	Emese Revfy <re.emese@gmail.com>,
	Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: [PATCH 2/6] Driver core: Fix memory leak on bus_register error path
Date: Mon, 26 Jul 2010 17:00:48 -0700	[thread overview]
Message-ID: <20100727000048.GB26421@kroah.com> (raw)
In-Reply-To: <4C4A4681.4070901@codeaurora.org>

On Fri, Jul 23, 2010 at 06:48:49PM -0700, Patrick Pannuto wrote:
> >>>  
> >>>  	retval = kset_register(&priv->subsys);
> >>> -	if (retval)
> >>> +	if (retval) {
> >>> +		kfree(priv->subsys.kobj.name);
> >>
> >> I don't think we want to bury the logic of how kobject names are handled
> >> up here in the bus code, right?  Shouldn't the subsys kobject name be
> >> able to be cleaned up on its own somehow instead?
> >>
> > 
> > So, my first instinct was to use kobject_cleanup, but a few lines above:
> > 
> > 	priv->subsys.kobj.ktype = &bus_ktype;
> > 
> > and bus_ktype's definition, with the notable absence of a release method:
> > 
> > static struct kobj_type bus_ktype = {
> > 	.sysfs_ops	= &bus_sysfs_ops,
> > };
> > 
> > which in kobject_cleanup would yield:
> > 
> > 	struct kobj_type *t = get_ktype(kobj);
> > 
> > 	if (t && !t->release)
> > 		pr_debug("kobject: '%s' (%p): does not have a release() "
> > 			 "function, it is broken and must be fixed.\n",
> > 			 kobject_name(kobj), kobj);
> > 
> > (if I understand everything correctly)
> > 
> 
> Thinking about this more, how does this ever work "correctly"? If we
> chase the 'normal' path from bus_unregister...
> 
> given bus->p->subsys.kobj.ktype = &bus_ktype
> 
> bus_unregister(struct bus_type *bus) {
>    kset_unregister(&bus->p->subsys) {
>       kobject_put(&k->kobj) {
>          kref_put(&kobj->kref, kobject_release) {
>             (assuming last ref)
>             kobject_cleanup(container_of(kref, struct kobject, kref)) {
>                	struct kobj_type *t = get_ktype(kobj);
> 
> 		if (t && !t->release)
> 			pr_debug("kobject: '%s' (%p): does not have a release() "
> 				 "function, it is broken and must be fixed.\n",
> 				 kobject_name(kobj), kobj);
> 
> Wouldn't this get hit every time a bus unregisters?  I feel like I'm
> missing something here?

You are, busses are wierd :)

I can't recall off the top of my head, but it all works out ok in the
end.

thanks,

greg k-h

  reply	other threads:[~2010-07-27  0:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 22:09 Possible memory leaks on driver core error paths Patrick Pannuto
2010-07-22 22:09 ` [PATCH 1/6] Driver core: Fix potential memory leak Patrick Pannuto
2010-07-22 23:39   ` Greg KH
2010-07-22 22:09 ` [PATCH 2/6] Driver core: Fix memory leak on bus_register error path Patrick Pannuto
2010-07-22 23:41   ` Greg KH
2010-07-24  1:19     ` Patrick Pannuto
2010-07-24  1:48       ` Patrick Pannuto
2010-07-27  0:00         ` Greg KH [this message]
2010-07-26 23:45       ` Greg KH
2010-07-22 22:09 ` [PATCH 3/6] Driver core: Fix memory leak on class_register " Patrick Pannuto
2010-07-22 23:41   ` Greg KH
2010-07-22 22:09 ` [PATCH 4/6] Driver core: Fix memory leak on sysdev_class_register " Patrick Pannuto
2010-07-22 23:41   ` Greg KH
2010-07-22 22:09 ` [Ocfs2-devel] [PATCH 5/6] ocfs2: Fix memory leak on mlog_sys_init " Patrick Pannuto
2010-07-22 22:09   ` Patrick Pannuto
2010-07-23 17:01   ` [Ocfs2-devel] " Pekka Enberg
2010-07-23 17:01     ` Pekka Enberg
2010-07-22 22:09 ` [PATCH 6/6] kobj: Fix memory leak on error path of kset_create_and_add Patrick Pannuto
2010-07-22 23:43   ` Greg KH

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=20100727000048.GB26421@kroah.com \
    --to=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ppannuto@codeaurora.org \
    --cc=re.emese@gmail.com \
    --cc=shemminger@vyatta.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.