]> git.karo-electronics.de Git - linux-beck.git/commit
Revert "cpumask: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write"
authorIngo Molnar <mingo@elte.hu>
Mon, 12 Jan 2009 09:49:53 +0000 (10:49 +0100)
committerIngo Molnar <mingo@elte.hu>
Mon, 12 Jan 2009 18:24:23 +0000 (19:24 +0100)
commit50c668d678fd01284799a6e4f1b91829d83cb9ed
treef3e129473515950d93a39b92c6ea2ebcbe3e5174
parent2bc1379712e74c5b99adaa6db433c14d8841ab4f
Revert "cpumask: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write"

This reverts commit 7503bfbae89eba07b46441a5d1594647f6b8ab7d.

Dieter Ries reported bootup soft-hangs and bisected it back to
this commit, and reverting this commit gave him a working system.

The commit introduces work_on_cpu() use into the cpufreq code,
but that is subtly problematic from a lock hierarchy POV: the
hotplug-cpu lock is an highlevel lock that is taken before
lowlevel locks, and in this codepath we are called with the
policy lock taken.

Dieter did not have lockdep enabled so we dont have a nice stack
trace proof for this, but using work_on_cpu() in such a lowlevel
place certainly looks wrong, so we revert the patch.

work_on_cpu() needs to be reworked to be more generally usable.

Reported-by: Dieter Ries <clip2@gmx.de>
Tested-by: Dieter Ries <clip2@gmx.de>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c