From: "Tobin C. Harding" <tobin@kernel.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>
Cc: "Tobin C. Harding" <tobin@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joe Lawrence <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] livepatch: Fix usage of kobject_init_and_add()
Date: Tue, 30 Apr 2019 10:15:32 +1000 [thread overview]
Message-ID: <20190430001534.26246-1-tobin@kernel.org> (raw)
Hi,
Currently there are a few places in kernel/livepatch/ which do not
correctly use kobject_init_and_add().
An error return from kobject_init_and_add() requires a call to
kobject_put().
The cleanup function after a successful call to kobject_init_and_add()
is kobject_del().
This set is part of an effort to check/fix all callsites of
kobject_init_and_add().
This set fixes all callsites under kernel/livepatch/
thanks,
Tobin.
Tobin C. Harding (2):
livepatch: Fix kobject memleak
livepatch: Use correct kobject cleanup function
kernel/livepatch/core.c | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
--
2.21.0
next reply other threads:[~2019-04-30 0:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 0:15 Tobin C. Harding [this message]
2019-04-30 0:15 ` [PATCH 1/2] livepatch: Fix kobject memleak Tobin C. Harding
2019-04-30 8:42 ` Greg Kroah-Hartman
2019-04-30 10:44 ` Miroslav Benes
2019-04-30 10:46 ` Greg Kroah-Hartman
2019-04-30 22:39 ` Tobin C. Harding
2019-04-30 14:56 ` Petr Mladek
2019-04-30 15:10 ` Greg Kroah-Hartman
2019-04-30 0:15 ` [PATCH 2/2] livepatch: Use correct kobject cleanup function Tobin C. Harding
2019-04-30 8:43 ` Greg Kroah-Hartman
2019-04-30 11:00 ` Miroslav Benes
2019-04-30 21:38 ` Tobin C. Harding
2019-04-30 15:08 ` Petr Mladek
2019-04-30 21:37 ` Tobin C. Harding
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=20190430001534.26246-1-tobin@kernel.org \
--to=tobin@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.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.