cpufreq: Fix kobject memleak
authorViresh Kumar <viresh.kumar@linaro.org>
Tue, 30 Apr 2019 06:05:52 +0000 (11:35 +0530)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Tue, 30 Apr 2019 08:54:23 +0000 (10:54 +0200)
commit4ebe36c94aed95de71a8ce6a6762226d31c938ee
treeaeeab4c5f504e0ad0df8f2d79c526f3b01eeb611
parent0a0cf5988f52247259d05d6661820f6fef08a6da
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: Viresh Kumar <viresh.kumar@linaro.org>
Reviewed-by: Tobin C. Harding <tobin@kernel.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpufreq/cpufreq.c
drivers/cpufreq/cpufreq_governor.c