diff options
author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2012-04-13 03:35:13 +0000 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-04-22 16:21:24 -0700 |
commit | 81cc5e7c4ed5bf9172b26bb3a7d019362dd3d204 (patch) | |
tree | 27d2366c0f53a43345a39fe4bcd38c8a0feab032 /arch/sparc/lib/ffs.S | |
parent | a2646264907ed038852b3ffdea9901cd5ea2305f (diff) | |
download | kernel_samsung_smdk4412-81cc5e7c4ed5bf9172b26bb3a7d019362dd3d204.zip kernel_samsung_smdk4412-81cc5e7c4ed5bf9172b26bb3a7d019362dd3d204.tar.gz kernel_samsung_smdk4412-81cc5e7c4ed5bf9172b26bb3a7d019362dd3d204.tar.bz2 |
sparc64: Eliminate obsolete __handle_softirq() function
commit 3d3eeb2ef26112a200785e5fca58ec58dd33bf1e upstream.
The invocation of softirq is now handled by irq_exit(), so there is no
need for sparc64 to invoke it on the trap-return path. In fact, doing so
is a bug because if the trap occurred in the idle loop, this invocation
can result in lockdep-RCU failures. The problem is that RCU ignores idle
CPUs, and the sparc64 trap-return path to the softirq handlers fails to
tell RCU that the CPU must be considered non-idle while those handlers
are executing. This means that RCU is ignoring any RCU read-side critical
sections in those handlers, which in turn means that RCU-protected data
can be yanked out from under those read-side critical sections.
The shiny new lockdep-RCU ability to detect RCU read-side critical sections
that RCU is ignoring located this problem.
The fix is straightforward: Make sparc64 stop manually invoking the
softirq handlers.
Reported-by: Meelis Roos <mroos@linux.ee>
Suggested-by: David Miller <davem@davemloft.net>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Tested-by: Meelis Roos <mroos@linux.ee>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/sparc/lib/ffs.S')
0 files changed, 0 insertions, 0 deletions