From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jacob Shin <jacob.shin@amd.com>
Cc: Tim Gardner <tim.gardner@canonical.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: od_set_powersave_bias: NULL pointer dereference
Date: Thu, 27 Jun 2013 21:53:15 +0530 [thread overview]
Message-ID: <CAKohpon6m0vX6_ZDrwUD-OBuD5WAysooJgYHSEXKstud3bh7Kw@mail.gmail.com> (raw)
In-Reply-To: <20130627162203.GB5324@jshin-Toonie>
On 27 June 2013 21:52, Jacob Shin <jacob.shin@amd.com> wrote:
> From 133f670aa1dc450fd37ba39081d046bf238c507b Mon Sep 17 00:00:00 2001
> From: Jacob Shin <jacob.shin@amd.com>
> Date: Thu, 27 Jun 2013 10:44:42 -0500
> Subject: [PATCH 1/1] cpufreq: don't leave stale policy pointer in
> cdbs->cur_policy
>
> Set ->cur_policy to NULL when stopping a governor. Otherwise, the
> ->cur_policy pointer may be stale on systems that
> have_governor_per_policy when a new policy is allocated due to CPU
> hotplug offline/online.
>
> Suggested-by: Viresh Kumar <viresh.kumar@linaro.org>
> Signed-off-by: Jacob Shin <jacob.shin@amd.com>
> ---
> drivers/cpufreq/cpufreq_governor.c | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
next prev parent reply other threads:[~2013-06-27 16:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 16:59 od_set_powersave_bias: NULL pointer dereference Tim Gardner
2013-06-25 6:56 ` Viresh Kumar
2013-06-25 16:19 ` Jacob Shin
2013-06-25 18:41 ` Tim Gardner
2013-06-25 22:39 ` Rafael J. Wysocki
2013-06-26 6:48 ` Viresh Kumar
2013-06-26 14:28 ` Jacob Shin
2013-06-26 14:32 ` Viresh Kumar
2013-06-26 14:35 ` Jacob Shin
2013-06-26 17:57 ` Jacob Shin
2013-06-27 7:02 ` Viresh Kumar
2013-06-27 14:55 ` Jacob Shin
2013-06-27 15:09 ` Viresh Kumar
2013-06-27 15:20 ` Viresh Kumar
2013-06-27 16:22 ` Jacob Shin
2013-06-27 16:23 ` Viresh Kumar [this message]
2013-06-27 15:21 ` Jacob Shin
2013-06-27 15:25 ` Viresh Kumar
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=CAKohpon6m0vX6_ZDrwUD-OBuD5WAysooJgYHSEXKstud3bh7Kw@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=jacob.shin@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tim.gardner@canonical.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).