summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLai Jiangshan <laijs@cn.fujitsu.com>2012-11-29 16:46:08 +0800
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2013-02-07 15:17:45 -0800
commit49271ca60645d64197b28c0835fed39f74b1a2d7 (patch)
tree361a1243a600d76ab94b44c7a9dd1d9dcc97c6b2
parent34a64b6bb64b5cf193932e2b4394c5284732e008 (diff)
srcu: Update synchronize_srcu_expedited()'s comments
Because synchronize_srcu_expedited() no longer uses synchronize_rcu_sched_expedited(), synchronize_srcu_expedited() no longer indirectly acquires any CPU-hotplug-related locks. This commit therefore updates the comments accordingly. Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
-rw-r--r--kernel/srcu.c11
1 files changed, 5 insertions, 6 deletions
diff --git a/kernel/srcu.c b/kernel/srcu.c
index f098f1768215..e34f2991ed41 100644
--- a/kernel/srcu.c
+++ b/kernel/srcu.c
@@ -477,12 +477,11 @@ EXPORT_SYMBOL_GPL(synchronize_srcu);
* Wait for an SRCU grace period to elapse, but be more aggressive about
* spinning rather than blocking when waiting.
*
- * Note that it is illegal to call this function while holding any lock
- * that is acquired by a CPU-hotplug notifier. It is also illegal to call
- * synchronize_srcu_expedited() from the corresponding SRCU read-side
- * critical section; doing so will result in deadlock. However, it is
- * perfectly legal to call synchronize_srcu_expedited() on one srcu_struct
- * from some other srcu_struct's read-side critical section, as long as
+ * Note that it is also illegal to call synchronize_srcu_expedited()
+ * from the corresponding SRCU read-side critical section;
+ * doing so will result in deadlock. However, it is perfectly legal
+ * to call synchronize_srcu_expedited() on one srcu_struct from some
+ * other srcu_struct's read-side critical section, as long as
* the resulting graph of srcu_structs is acyclic.
*/
void synchronize_srcu_expedited(struct srcu_struct *sp)