The patch titled
     Subject: drivers/cpuidle/coupled.c: fix sleeping while atomic in cpu 
notifier
has been removed from the -mm tree.  Its filename was
     drivers-cpuidle-coupledc-fix-sleeping-while-atomic-in-cpu-notifier.patch

This patch was dropped because it was merged into mainline or a subsystem tree

------------------------------------------------------
From: Colin Cross <[email protected]>
Subject: drivers/cpuidle/coupled.c: fix sleeping while atomic in cpu notifier

The cpu hotplug notifier gets called in both atomic and non-atomic
contexts, it is not always safe to lock a mutex.  Filter out all events
except the six necessary ones, which are all sleepable, before taking the
mutex.

Signed-off-by: Colin Cross <[email protected]>
Acked-by: Santosh Shilimkar <[email protected]>
Cc: Srivatsa S. Bhat <[email protected]>
Cc: Len Brown <[email protected]>
Cc: "Brown, Len" <[email protected]>
Cc: <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
---

 drivers/cpuidle/coupled.c |   12 ++++++++++++
 1 file changed, 12 insertions(+)

diff -puN 
drivers/cpuidle/coupled.c~drivers-cpuidle-coupledc-fix-sleeping-while-atomic-in-cpu-notifier
 drivers/cpuidle/coupled.c
--- 
a/drivers/cpuidle/coupled.c~drivers-cpuidle-coupledc-fix-sleeping-while-atomic-in-cpu-notifier
+++ a/drivers/cpuidle/coupled.c
@@ -678,6 +678,18 @@ static int cpuidle_coupled_cpu_notify(st
        int cpu = (unsigned long)hcpu;
        struct cpuidle_device *dev;
 
+       switch (action & ~CPU_TASKS_FROZEN) {
+       case CPU_UP_PREPARE:
+       case CPU_DOWN_PREPARE:
+       case CPU_ONLINE:
+       case CPU_DEAD:
+       case CPU_UP_CANCELED:
+       case CPU_DOWN_FAILED:
+               break;
+       default:
+               return NOTIFY_OK;
+       }
+
        mutex_lock(&cpuidle_lock);
 
        dev = per_cpu(cpuidle_devices, cpu);
_

Patches currently in -mm which might be from [email protected] are

origin.patch
linux-next.patch

--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to