From: Ingo Molnar <mingo@kernel.org>
To: "Tobin C. Harding" <tobin@kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/cpufreq: Fix kobject memleak
Date: Tue, 30 Apr 2019 06:22:57 +0200 [thread overview]
Message-ID: <20190430042257.GA73609@gmail.com> (raw)
In-Reply-To: <20190430001144.24890-1-tobin@kernel.org>
* Tobin C. Harding <tobin@kernel.org> wrote:
> Currently error return from kobject_init_and_add() is not followed by a
> call to kobject_put(). This means there is a memory leak.
>
> Add call to kobject_put() in error path of kobject_init_and_add().
> ---
> kernel/sched/cpufreq_schedutil.c | 1 +
> 1 file changed, 1 insertion(+)
I've added your:
Signed-off-by: Tobin C. Harding <tobin@kernel.org>
Which I suppose you intended to include?
Thanks,
Ingo
next prev parent reply other threads:[~2019-04-30 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 0:11 [PATCH] sched/cpufreq: Fix kobject memleak Tobin C. Harding
2019-04-30 4:22 ` Ingo Molnar [this message]
2019-04-30 5:52 ` [tip:sched/urgent] " tip-bot for Tobin C. Harding
2019-04-30 5:56 ` Viresh Kumar
2019-04-30 6:27 ` Tobin C. Harding
2019-04-30 6:01 ` tip-bot for 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=20190430042257.GA73609@gmail.com \
--to=mingo@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tobin@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 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.