diff options
author | Paul E. McKenney <paulmck@kernel.org> | 2021-04-29 11:18:01 -0700 |
---|---|---|
committer | Paul E. McKenney <paulmck@kernel.org> | 2021-05-13 09:13:23 -0700 |
commit | 1893afd63409111c6edcee9d6e1196fc06cf4fd7 (patch) | |
tree | 7e69c09686f67289eacdabcd4f25e8471230c93e /security/yama | |
parent | 76c8eaafe4f061f3790112842a2fbb297e4bea88 (diff) | |
download | linux-stable-1893afd63409111c6edcee9d6e1196fc06cf4fd7.tar.gz linux-stable-1893afd63409111c6edcee9d6e1196fc06cf4fd7.tar.bz2 linux-stable-1893afd63409111c6edcee9d6e1196fc06cf4fd7.zip |
rcu: Improve comments describing RCU read-side critical sections
There are a number of places that call out the fact that preempt-disable
regions of code now act as RCU read-side critical sections, where
preempt-disable regions of code include irq-disable regions of code,
bh-disable regions of code, hardirq handlers, and NMI handlers. However,
someone relying solely on (for example) the call_rcu() header comment
might well have no idea that preempt-disable regions of code have RCU
semantics.
This commit therefore updates the header comments for
call_rcu(), synchronize_rcu(), rcu_dereference_bh_check(), and
rcu_dereference_sched_check() to call out these new(ish) forms of RCU
readers.
Reported-by: Michel Lespinasse <michel@lespinasse.org>
[ paulmck: Apply Matthew Wilcox and Michel Lespinasse feedback. ]
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'security/yama')
0 files changed, 0 insertions, 0 deletions