rcu: Remove srcu_read_lock_raw() and srcu_read_unlock_raw().

These interfaces never did get used, so this commit removes them,
their rcutorture tests, and documentation referencing them.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Lai Jiangshan <laijs@cn.fujitsu.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>

1 files changed, 0 insertions, 6 deletions

diff --git a/Documentation/RCU/checklist.txt b/Documentation/RCU/checklist.txt
index 79e789b8b8ea..7703ec73a9bb 100644
--- a/Documentation/RCU/checklist.txt
+++ b/Documentation/RCU/checklist.txt
@@ -354,12 +354,6 @@ over a rather long period of time, but improvements are always welcome!
         using RCU rather than SRCU, because RCU is almost always faster
         and easier to use than is SRCU.
 
-        If you need to enter your read-side critical section in a
-        hardirq or exception handler, and then exit that same read-side
-        critical section in the task that was interrupted, then you need
-        to srcu_read_lock_raw() and srcu_read_unlock_raw(), which avoid
-        the lockdep checking that would otherwise this practice illegal.
-
         Also unlike other forms of RCU, explicit initialization
         and cleanup is required via init_srcu_struct() and
         cleanup_srcu_struct().  These are passed a "struct srcu_struct"