From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Aaron Plattner <aplattner@nvidia.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v2] cpufreq: unlock when failing cpufreq_update_policy()
Date: Thu, 19 Jun 2014 01:57:54 +0200 [thread overview]
Message-ID: <3158268.Ad2sxChQ89@vostro.rjw.lan> (raw)
In-Reply-To: <1403116052-4659-1-git-send-email-aplattner@nvidia.com>
On Wednesday, June 18, 2014 11:27:32 AM Aaron Plattner wrote:
> 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.
>
> v2: Delete the no_policy label and just return early if policy is NULL.
>
> 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-/
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Signed-off-by: Aaron Plattner <aplattner@nvidia.com>
Applied, thanks!
> ---
> v1 of this was tested by the user affected by the problem, but I don't have his
> email address so I can't add it as a Tested-by line.
>
> drivers/cpufreq/cpufreq.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index aed2b0cb83dc..62259d27f03e 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -2242,10 +2242,8 @@ int cpufreq_update_policy(unsigned int cpu)
> struct cpufreq_policy new_policy;
> int ret;
>
> - if (!policy) {
> - ret = -ENODEV;
> - goto no_policy;
> - }
> + if (!policy)
> + return -ENODEV;
>
> down_write(&policy->rwsem);
>
> @@ -2264,7 +2262,7 @@ int cpufreq_update_policy(unsigned int cpu)
> new_policy.cur = cpufreq_driver->get(cpu);
> if (WARN_ON(!new_policy.cur)) {
> ret = -EIO;
> - goto no_policy;
> + goto unlock;
> }
>
> if (!policy->cur) {
> @@ -2279,10 +2277,10 @@ int cpufreq_update_policy(unsigned int cpu)
>
> ret = cpufreq_set_policy(policy, &new_policy);
>
> +unlock:
> up_write(&policy->rwsem);
>
> cpufreq_cpu_put(policy);
> -no_policy:
> return ret;
> }
> EXPORT_SYMBOL(cpufreq_update_policy);
>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
prev parent reply other threads:[~2014-06-18 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 0:12 [PATCH] " Aaron Plattner
2014-06-18 7:40 ` Viresh Kumar
2014-06-18 14:39 ` Aaron Plattner
2014-06-18 14:41 ` Viresh Kumar
2014-06-18 18:27 ` [PATCH v2] " Aaron Plattner
2014-06-18 23:57 ` Rafael J. Wysocki [this message]
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=3158268.Ad2sxChQ89@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=aplattner@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®