cpuidle: move driver checking within the lock section
authorDaniel Lezcano <daniel.lezcano@linaro.org>
Wed, 31 Oct 2012 16:44:46 +0000 (16:44 +0000)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Wed, 14 Nov 2012 23:34:22 +0000 (00:34 +0100)
The code is racy and the check with cpuidle_curr_driver should be
done under the lock.

I don't find a path in the different drivers where that could happen
because the arch specific drivers are written in such way it is not
possible to register a driver while it is unregistered, except maybe
in a very improbable case when "intel_idle" and "processor_idle" are
competing. One could unregister a driver, while the other one is
registering.

Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Acked-by: Peter De Schrijver <pdeschrijver@nvidia.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
drivers/cpuidle/driver.c

index 39ba8e181e96a98885e1b910a87e5cba2beed37b..3e5907569233c4792219166a646dfda00769f5cc 100644 (file)
@@ -85,17 +85,9 @@ EXPORT_SYMBOL_GPL(cpuidle_get_driver);
  */
 void cpuidle_unregister_driver(struct cpuidle_driver *drv)
 {
-       if (drv != cpuidle_curr_driver) {
-               WARN(1, "invalid cpuidle_unregister_driver(%s)\n",
-                       drv->name);
-               return;
-       }
-
        spin_lock(&cpuidle_driver_lock);
-
-       if (!WARN_ON(drv->refcnt > 0))
+       if (drv == cpuidle_curr_driver && !WARN_ON(drv->refcnt > 0))
                cpuidle_curr_driver = NULL;
-
        spin_unlock(&cpuidle_driver_lock);
 }
 EXPORT_SYMBOL_GPL(cpuidle_unregister_driver);