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

2016-03-18 Thread Rafael J. Wysocki
On Saturday, March 12, 2016 06:52:37 AM Viresh Kumar wrote: > On 11-03-16, 09:43, 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 guaran

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

2016-03-11 Thread Viresh Kumar
On 11-03-16, 09:43, 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 during the call. This

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

2016-03-11 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