path: root/Documentation/RCU
diff options
authorSeongJae Park <>2020-01-06 21:07:58 +0100
committerPaul E. McKenney <>2020-02-27 07:03:13 -0800
commit3282b0469248ab25b3f40b95e9a3d357c9d946d5 (patch)
treeb6e9106dc75a05a93bdb6a41773c5be3757227c9 /Documentation/RCU
parentc50a871409dc664f2f89d11926d9a6b8ab7f5b07 (diff)
doc/RCU/listRCU: Update example function name
listRCU.rst document gives an example with 'ipc_lock()', but the function has dropped off by commit 82061c57ce93 ("ipc: drop ipc_lock()"). Because the main logic of 'ipc_lock()' has melded in 'shm_lock()' by the commit, this commit updates the document to use 'shm_lock()' instead. Reviewed-by: Madhuparna Bhowmik <> Signed-off-by: SeongJae Park <> Signed-off-by: Paul E. McKenney <>
Diffstat (limited to 'Documentation/RCU')
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/RCU/listRCU.rst b/Documentation/RCU/listRCU.rst
index e768f56e8fa3..2a643e293fb4 100644
--- a/Documentation/RCU/listRCU.rst
+++ b/Documentation/RCU/listRCU.rst
@@ -286,11 +286,11 @@ time the external state changes before Linux becomes aware of the change,
additional RCU-induced staleness is generally not a problem.
However, there are many examples where stale data cannot be tolerated.
-One example in the Linux kernel is the System V IPC (see the ipc_lock()
-function in ipc/util.c). This code checks a *deleted* flag under a
+One example in the Linux kernel is the System V IPC (see the shm_lock()
+function in ipc/shm.c). This code checks a *deleted* flag under a
per-entry spinlock, and, if the *deleted* flag is set, pretends that the
entry does not exist. For this to be helpful, the search function must
-return holding the per-entry lock, as ipc_lock() does in fact do.
+return holding the per-entry spinlock, as shm_lock() does in fact do.
.. _quick_quiz: