From: "Tobin C. Harding" <me@tobin.cc>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: cl@linux.com, tycho@tycho.ws, willy@infradead.org,
linux-kernel@vger.kernel.org
Subject: memleak around kobject_init_and_add()
Date: Sat, 27 Apr 2019 18:13:30 +1000 [thread overview]
Message-ID: <20190427081330.GA26788@eros.localdomain> (raw)
(Note at bottom on reasons for 'To' list 'Cc' list)
Hi,
kobject_init_and_add() seems to be routinely misused. A failed call to this
function requires a call to kobject_put() otherwise we leak memory.
Examples memleaks can be seen in:
mm/slub.c
fs/btrfs/sysfs.c
fs/xfs/xfs_sysfs.h: xfs_sysfs_init()
Question: Do we fix the misuse or fix the API?
$ git grep kobject_init_and_add | wc -l
117
Either way, we will have to go through all 117 call sites and check them. I
don't mind fixing them all but I don't want to do it twice because I chose the
wrong option. Reaching out to those more experienced for a suggestion please.
Fix the API
-----------
Typically init functions do not require cleanup if they fail, this argument
leads to this patch
diff --git a/lib/kobject.c b/lib/kobject.c
index aa89edcd2b63..62328054bbd0 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -453,6 +453,9 @@ int kobject_init_and_add(struct kobject *kobj, struct kobj_type *ktype,
retval = kobject_add_varg(kobj, parent, fmt, args);
va_end(args);
+ if (retval)
+ kobject_put(kobj);
+
return retval;
}
EXPORT_SYMBOL_GPL(kobject_init_and_add);
Fix all the call sites
----------------------
Go through all 117 call sites and add kobj_put() in the error path.
This example from mm/slub.c
diff --git a/mm/slub.c b/mm/slub.c
index d30ede89f4a6..84a9d6c06c27 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -5756,8 +5756,10 @@ static int sysfs_slab_add(struct kmem_cache *s)
s->kobj.kset = kset;
err = kobject_init_and_add(&s->kobj, &slab_ktype, NULL, "%s", name);
- if (err)
+ if (err) {
+ kobject_put(&s->kobj);
goto out;
+ }
err = sysfs_create_group(&s->kobj, &slab_attr_group);
if (err)
thanks,
Tobin.
This is a Saturday afternoon 'drinking some wine, hacking on the kernel'
email. Sending it to the lib/kobject.c maintainers for obvious
reasons. CC'd a few extra people who I thought might be interested to
take the weight of Greg and Rafael :)
next reply other threads:[~2019-04-27 8:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-27 8:13 Tobin C. Harding [this message]
2019-04-27 19:28 ` Greg Kroah-Hartman
2019-04-27 23:33 ` Tobin C. Harding
2019-04-28 1:19 ` Tobin C. Harding
2019-04-28 16:14 ` Greg Kroah-Hartman
2019-04-28 22:46 ` Tobin C. Harding
2019-05-01 21:56 ` Tobin C. Harding
2019-05-02 7:17 ` Greg Kroah-Hartman
2019-05-02 7:28 ` Greg Kroah-Hartman
2019-05-02 8:19 ` Tobin C. Harding
2019-05-02 10:22 ` [PATCH] kobject: clean up the kobject add documentation a bit more Greg Kroah-Hartman
2019-05-03 1:25 ` Tobin C. Harding
2019-05-03 6:27 ` Greg Kroah-Hartman
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=20190427081330.GA26788@eros.localdomain \
--to=me@tobin.cc \
--cc=cl@linux.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tycho@tycho.ws \
--cc=willy@infradead.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®