[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190430062707.GB32393@eros.localdomain>
Date: Tue, 30 Apr 2019 16:27:07 +1000
From: "Tobin C. Harding" <me@...in.cc>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: mingo@...nel.org, torvalds@...ux-foundation.org,
gregkh@...uxfoundation.org, hpa@...or.com, tglx@...utronix.de,
vincent.guittot@...aro.org, peterz@...radead.org,
rafael.j.wysocki@...el.com, tobin@...nel.org,
linux-kernel@...r.kernel.org, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/urgent] sched/cpufreq: Fix kobject memleak
On Tue, Apr 30, 2019 at 11:26:27AM +0530, Viresh Kumar wrote:
> On 29-04-19, 22:52, tip-bot for Tobin C. Harding wrote:
> > Commit-ID: 8bf7ab9c79f3d1a5f02ebac369f656de9ec0aca8
> > Gitweb: https://git.kernel.org/tip/8bf7ab9c79f3d1a5f02ebac369f656de9ec0aca8
> > Author: Tobin C. Harding <tobin@...nel.org>
> > AuthorDate: Tue, 30 Apr 2019 10:11:44 +1000
> > Committer: Ingo Molnar <mingo@...nel.org>
> > CommitDate: Tue, 30 Apr 2019 06:24:09 +0200
> >
> > sched/cpufreq: Fix kobject memleak
> >
> > Currently the error return path from kobject_init_and_add() is not
> > followed by a call to kobject_put() - which means we are leaking
> > the kobject.
> >
> > Fix it by adding a call to kobject_put() in the error path of
> > kobject_init_and_add().
> >
> > Signed-off-by: Tobin C. Harding <tobin@...nel.org>
> > Add call to kobject_put() in error path of kobject_init_and_add().
>
> This should have been present before the signed-off ?
Thanks. Some face palm fails on this patch. Its hard to get good help
:)
Tobin
Powered by blists - more mailing lists