summaryrefslogtreecommitdiff
path: root/drivers/cpufreq/exynos5250-cpufreq.c
diff options
context:
space:
mode:
authorAaron Plattner <aplattner@nvidia.com>2014-06-18 11:27:32 -0700
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2014-06-18 21:52:20 +0200
commitfefa8ff810c5ab4c4206aed9d159c4d6fe8d4f1c (patch)
tree6118b6695bc29d4bad0a0cdb36ee295903574711 /drivers/cpufreq/exynos5250-cpufreq.c
parent51d211e9c334b9eca3505f4052afa660c3e0606b (diff)
cpufreq: unlock when failing cpufreq_update_policy()
Commit bd0fa9bb455d introduced a failure path to cpufreq_update_policy() if cpufreq_driver->get(cpu) returns NULL. However, it jumps to the 'no_policy' label, which exits without unlocking any of the locks the function acquired earlier. This causes later calls into cpufreq to hang. Fix this by creating a new 'unlock' label and jumping to that instead. Fixes: bd0fa9bb455d ("cpufreq: Return error if ->get() failed in cpufreq_update_policy()") Link: https://devtalk.nvidia.com/default/topic/751903/kernel-3-15-and-nv-drivers-337-340-failed-to-initialize-the-nvidia-kernel-module-gtx-550-ti-/ Signed-off-by: Aaron Plattner <aplattner@nvidia.com> Cc: 3.15+ <stable@vger.kernel.org> # 3.15+ Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq/exynos5250-cpufreq.c')
0 files changed, 0 insertions, 0 deletions