Re: [PATCH 4/5] cpufreq, policy->initialized count must be atomic

[Viresh Kumar]

On 5 November 2014 20:23, Prarit Bhargava <prarit@xxxxxxxxxx> 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 :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/