diff options
| author | Viresh Kumar | 2015-05-12 08:52:51 +0200 |
|---|---|---|
| committer | Rafael J. Wysocki | 2015-05-15 02:46:45 +0200 |
| commit | 18bf3a124ef87fe43045cbf13dff7ea7e3a94aa3 (patch) | |
| tree | ca480f2d5808574d85711b1be1872cf3a7ba01f7 /include/linux/swiotlb.h | |
| parent | cpufreq: Manage governor usage history with 'policy->last_governor' (diff) | |
| download | kernel-qcow2-linux-18bf3a124ef87fe43045cbf13dff7ea7e3a94aa3.tar.gz kernel-qcow2-linux-18bf3a124ef87fe43045cbf13dff7ea7e3a94aa3.tar.xz kernel-qcow2-linux-18bf3a124ef87fe43045cbf13dff7ea7e3a94aa3.zip | |
cpufreq: Mark policy->governor = NULL for inactive policies
Later commits would change the way policies are managed today. Policies
wouldn't be freed on cpu hotplug (currently they aren't freed on
suspend), and while the CPU is offline, the sysfs cpufreq files would
still be present.
Because we don't mark policy->governor as NULL, it still contains
pointer of the last used governor. And if the governor is removed, while
all the CPUs of a policy are hotplugged out, this pointer wouldn't be
valid anymore. And if we try to read the 'scaling_governor', etc. from
sysfs, it will result in kernel OOPs.
To prevent this, mark policy->governor as NULL for all inactive policies
while the governor is removed from kernel.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'include/linux/swiotlb.h')
0 files changed, 0 insertions, 0 deletions