Re: [PATCH] cpufreq: Make cpufreq_quick_get() safe to call.

2016-03-10 Thread Rafael J. Wysocki
On Thu, Mar 10, 2016 at 11:20 PM, Rafael J. Wysocki wrote: > On Thursday, March 10, 2016 04:10:36 PM Richard Cochran wrote: >> The function, cpufreq_quick_get, accesses the global 'cpufreq_driver' and >> its fields without taking the associated lock, cpufreq_driver_lock. >> >> Without the locking,

Re: [PATCH] cpufreq: Make cpufreq_quick_get() safe to call.

2016-03-10 Thread Rafael J. Wysocki
On Thursday, March 10, 2016 04:10:36 PM Richard Cochran wrote: > The function, cpufreq_quick_get, accesses the global 'cpufreq_driver' and > its fields without taking the associated lock, cpufreq_driver_lock. > > Without the locking, nothing guarantees that 'cpufreq_driver' remains > consistent du

[PATCH] cpufreq: Make cpufreq_quick_get() safe to call.

2016-03-10 Thread Richard Cochran
The function, cpufreq_quick_get, accesses the global 'cpufreq_driver' and its fields without taking the associated lock, cpufreq_driver_lock. Without the locking, nothing guarantees that 'cpufreq_driver' remains consistent during the call. This patch fixes the issue by taking the lock before acce