Re: [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions

On 6 March 2014 09:23, Rafael J. Wysocki wrote: > On Tuesday, March 04, 2014 12:42:15 PM Aaron Plattner wrote: >> If a module calls cpufreq_get while cpufreq is initializing, it's possible >> for >> it to be called after cpufreq_driver is set but before cpufreq_cpu_data is >> written during subsy

Re: [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions

On Wednesday, March 05, 2014 05:14:26 PM Aaron Plattner wrote: > On 03/05/14 17:23, Rafael J. Wysocki wrote: > > On Tuesday, March 04, 2014 12:42:15 PM Aaron Plattner wrote: > >> If a module calls cpufreq_get while cpufreq is initializing, it's possible > >> for > >> it to be called after cpufreq_

Re: [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions

On 03/05/14 17:23, Rafael J. Wysocki wrote: On Tuesday, March 04, 2014 12:42:15 PM Aaron Plattner wrote: If a module calls cpufreq_get while cpufreq is initializing, it's possible for it to be called after cpufreq_driver is set but before cpufreq_cpu_data is written during subsys_interface_regis

Re: [PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions

On Tuesday, March 04, 2014 12:42:15 PM Aaron Plattner wrote: > If a module calls cpufreq_get while cpufreq is initializing, it's possible for > it to be called after cpufreq_driver is set but before cpufreq_cpu_data is > written during subsys_interface_register. This happens because cpufreq_get >

[PATCH] cpufreq: use cpufreq_cpu_get to avoid cpufreq_get race conditions

If a module calls cpufreq_get while cpufreq is initializing, it's possible for it to be called after cpufreq_driver is set but before cpufreq_cpu_data is written during subsys_interface_register. This happens because cpufreq_get doesn't take the cpufreq_driver_lock around its use of cpufreq_cpu_da