sparc64: Eliminate obsolete __handle_softirq() function
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>
Fri, 13 Apr 2012 03:35:13 +0000 (03:35 +0000)
committerWilly Tarreau <w@1wt.eu>
Sun, 7 Oct 2012 21:41:03 +0000 (23:41 +0200)
commit3eaebbc174f2804441bc0b4cfdf2f864cbf39f57
treecb445c556f13900aae1e489ea58832ff2d7de881
parentb655a07ff73516c3e7d588ef65f17b96953dca00
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>
Signed-off-by: Willy Tarreau <w@1wt.eu>
arch/sparc/kernel/rtrap_64.S