Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 5ef98a63 authored by Paul E. McKenney's avatar Paul E. McKenney
Browse files

srcu: Fix typos in __call_srcu() header comment 



This commit simply changes some copy-pasta call_rcu() instances to
the correct call_srcu().

Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
parent ce397d21

kernel/rcu/srcutree.c

+4 −4
Original line number Diff line number Diff line
@@ -823,17 +823,17 @@ static void srcu_leak_callback(struct rcu_head *rhp) 
 * more than one CPU, this means that when "func()" is invoked, each CPU

 * is guaranteed to have executed a full memory barrier since the end of

 * its last corresponding SRCU read-side critical section whose beginning

 * preceded the call to call_rcu().  It also means that each CPU executing

 * preceded the call to call_srcu().  It also means that each CPU executing

 * an SRCU read-side critical section that continues beyond the start of

 * "func()" must have executed a memory barrier after the call_rcu()

 * "func()" must have executed a memory barrier after the call_srcu()

 * but before the beginning of that SRCU read-side critical section.

 * Note that these guarantees include CPUs that are offline, idle, or

 * executing in user mode, as well as CPUs that are executing in the kernel.

 *

 * Furthermore, if CPU A invoked call_rcu() and CPU B invoked the

 * Furthermore, if CPU A invoked call_srcu() and CPU B invoked the

 * resulting SRCU callback function "func()", then both CPU A and CPU

 * B are guaranteed to execute a full memory barrier during the time

 * interval between the call to call_rcu() and the invocation of "func()".

 * interval between the call to call_srcu() and the invocation of "func()".

 * This guarantee applies even if CPU A and CPU B are the same CPU (but

 * again only if the system has more than one CPU).

 *