summaryrefslogtreecommitdiff
path: root/Documentation/device-mapper/dm-flakey.txt
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2018-06-29 00:45:25 +0300
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2018-08-31 02:02:38 +0300
commitd28139c4e96713d52a300fb9036c5be2f45e0741 (patch)
tree745b5cc3e1af736fcdb43367454335bf49bb510d /Documentation/device-mapper/dm-flakey.txt
parente11ec65cc8d63c41fc468363b65826a5ae4b8c66 (diff)
downloadlinux-d28139c4e96713d52a300fb9036c5be2f45e0741.tar.xz
rcu: Apply RCU-bh QSes to RCU-sched and RCU-preempt when safe
One necessary step towards consolidating the three flavors of RCU is to make sure that the resulting consolidated "one flavor to rule them all" correctly handles networking denial-of-service attacks. One thing that allows RCU-bh to do so is that __do_softirq() invokes rcu_bh_qs() every so often, and so something similar has to happen for consolidated RCU. This must be done carefully. For example, if a preemption-disabled region of code takes an interrupt which does softirq processing before returning, consolidated RCU must ignore the resulting rcu_bh_qs() invocations -- preemption is still disabled, and that means an RCU reader for the consolidated flavor. This commit therefore creates a new rcu_softirq_qs() that is called only from the ksoftirqd task, thus avoiding the interrupted-a-preempted-region problem. This new rcu_softirq_qs() function invokes rcu_sched_qs(), rcu_preempt_qs(), and rcu_preempt_deferred_qs(). The latter call handles any deferred quiescent states. Note that __do_softirq() still invokes rcu_bh_qs(). It will continue to do so until a later stage of cleanup when the RCU-bh flavor is removed. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> [ paulmck: Fix !SMP issue located by kbuild test robot. ]
Diffstat (limited to 'Documentation/device-mapper/dm-flakey.txt')
0 files changed, 0 insertions, 0 deletions