| commit | 4b96b1a10cb00c867103b21f0f2a6c91b705db11 | |
| author | Gautham R Shenoy <ego@in.ibm.com> | |
| Mon, 6 Nov 2006 07:52:04 +0000 (5 23:52 -0800) | ||
| committer | Linus Torvalds <torvalds@g5.osdl.org> | |
| Mon, 6 Nov 2006 09:46:22 +0000 (6 01:46 -0800) | ||
| tree | 25b95e00b413025682b933da182caca2a048a475 | treesnapshot (tar.gz zip) |
| parent | d1ed6a3ea10aa7b199c434f6ffd1b6761896567a | commitdiff |
[PATCH] Fix the spurious unlock_cpu_hotplug false warnings
Cpu-hotplug locking has a minor race case caused because of setting the
variable "recursive" to NULL *after* releasing the cpu_bitmask_lock in the
function unlock_cpu_hotplug,instead of doing so before releasing the
cpu_bitmask_lock.
This was the cause of most of the recent false spurious lock_cpu_unlock
warnings.
This should fix the problem reported by Martin Lorenz reported in
http://lkml.org/lkml/2006/10/29/127.
Thanks to Srinivasa DS for pointing it out.
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Cpu-hotplug locking has a minor race case caused because of setting the
variable "recursive" to NULL *after* releasing the cpu_bitmask_lock in the
function unlock_cpu_hotplug,instead of doing so before releasing the
cpu_bitmask_lock.
This was the cause of most of the recent false spurious lock_cpu_unlock
warnings.
This should fix the problem reported by Martin Lorenz reported in
http://lkml.org/lkml/2006/10/29/127.
Thanks to Srinivasa DS for pointing it out.
Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
| kernel/cpu.c | diffblobblamehistory |