From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM list <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH] cpufreq: Avoid using inactive policies
Date: Fri, 18 Nov 2016 08:47:50 +0530 [thread overview]
Message-ID: <20161118031750.GD3110@vireshk-i7> (raw)
In-Reply-To: <2600582.kqN5q7nCq0@vostro.rjw.lan>
On 17-11-16, 16:08, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> There are two places in the cpufreq core in which low-level driver
> callbacks may be invoked for an inactive cpufreq policy, which isn't
> guaranteed to work in general. Both are due to possible races with
> CPU offline.
>
> First, in cpufreq_get(), the policy may become inactive after
> the check against policy->cpus in cpufreq_cpu_get() and before
> policy->rwsem is acquired, in which case using the policy going
> forward may not be correct.
>
> Second, an analogous situation is possible in cpufreq_update_policy().
>
> Avoid using inactive policies by adding policy_is_inactive() checks
> to the code in the above places.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/cpufreq/cpufreq.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> Index: linux-pm/drivers/cpufreq/cpufreq.c
> ===================================================================
> --- linux-pm.orig/drivers/cpufreq/cpufreq.c
> +++ linux-pm/drivers/cpufreq/cpufreq.c
> @@ -1526,7 +1526,10 @@ unsigned int cpufreq_get(unsigned int cp
>
> if (policy) {
> down_read(&policy->rwsem);
> - ret_freq = __cpufreq_get(policy);
> +
> + if (!policy_is_inactive(policy))
> + ret_freq = __cpufreq_get(policy);
> +
> up_read(&policy->rwsem);
>
> cpufreq_cpu_put(policy);
> @@ -2265,6 +2268,9 @@ int cpufreq_update_policy(unsigned int c
>
> down_write(&policy->rwsem);
>
> + if (policy_is_inactive(policy))
You also need to set some value to 'ret' as it is uninitialized right now.
> + goto unlock;
> +
> pr_debug("updating policy for CPU %u\n", cpu);
> memcpy(&new_policy, policy, sizeof(*policy));
> new_policy.min = policy->user_policy.min;
--
viresh
next prev parent reply other threads:[~2016-11-18 3:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 15:08 [PATCH] cpufreq: Avoid using inactive policies Rafael J. Wysocki
2016-11-18 3:17 ` Viresh Kumar [this message]
2016-11-18 12:20 ` Rafael J. Wysocki
2016-11-18 12:25 ` Rafael J. Wysocki
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=20161118031750.GD3110@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).