Messages in this thread | | | Date | Tue, 11 Nov 2014 09:25:38 +0530 | Subject | Re: [PATCH 4/5] cpufreq, policy->initialized count must be atomic | From | Viresh Kumar <> |
| |
On 5 November 2014 20:23, Prarit Bhargava <prarit@redhat.com> wrote: > The policy->initialized value can be modified from several cpus concurrently if > !CPUFREQ_HAVE_GOVERNOR_PER_POLICY. This leads to a situation where a > governor maybe switched out even though the governor->initialized is greater > than one. It must be switched to atomic_t and protected with a mutex to > make sure that future read/writes obtain the correct data.
Can you show a sequence of events to demonstrate the race you are talking about? As far as I can see, there are no races :)
| |