From: "Paul E. McKenney" Fix to broken comment to synchronize_rcu() noted by Keith Owens. Also add sentence noting that synchronize_sched() and synchronize_rcu() are not necessarily identical. Signed-off-by: Paul E. McKenney Cc: Keith Owens Cc: Stephen Hemminger Signed-off-by: Andrew Morton --- include/linux/rcupdate.h | 5 ++++- 1 files changed, 4 insertions(+), 1 deletion(-) diff -puN include/linux/rcupdate.h~fix-comment-to-synchronize_sched include/linux/rcupdate.h --- devel/include/linux/rcupdate.h~fix-comment-to-synchronize_sched 2006-01-25 11:08:48.000000000 -0800 +++ devel-akpm/include/linux/rcupdate.h 2006-01-25 11:08:48.000000000 -0800 @@ -238,11 +238,14 @@ extern int rcu_pending(int cpu); * This means that all preempt_disable code sequences, including NMI and * hardware-interrupt handlers, in progress on entry will have completed * before this primitive returns. However, this does not guarantee that - * softirq handlers will have completed, since in some kernels + * softirq handlers will have completed, since in some kernels, these + * handlers can run in process context, and can block. * * This primitive provides the guarantees made by the (deprecated) * synchronize_kernel() API. In contrast, synchronize_rcu() only * guarantees that rcu_read_lock() sections will have completed. + * In "classic RCU", these two guarantees happen to be one and + * the same, but can differ in realtime RCU implementations. */ #define synchronize_sched() synchronize_rcu() _