summaryrefslogtreecommitdiff
path: root/net/netrom/nr_route.c
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2016-12-12 12:17:24 +0000
committerMark Brown <broonie@kernel.org>2016-12-12 12:17:24 +0000
commitbed69721b67aeb3616e983ed32acc131968188f5 (patch)
tree8968860c3bf057df68a5a77dd9e1ed8c44db7524 /net/netrom/nr_route.c
parent6b46856246592f860840acf32fcb732111c1c9eb (diff)
parent88f0e3a5e6ed674f485d3a09d53c2ead0000378d (diff)
parent85b037442e3f0e84296ab1010fd6b057eee18496 (diff)
parent30103b5b6432a51c3822a26dc340e35d91237f39 (diff)
parentcc9b94029e9ef51787af908e9856b1eed314bc00 (diff)
Merge remote-tracking branches 'regulator/topic/arizona', 'regulator/topic/bypass', 'regulator/topic/error' and 'regulator/topic/fixed' into regulator-next
the existing rcu_scheduler_starting() function which causes all synchronous grace periods to take the expedited path. The expedited path now checks this flag, using the requesting task to drive the expedited grace period forward during the mid-boot phase. Finally, this flag is updated by a core_initcall() function named rcu_exp_runtime_mode(), which causes the runtime codepaths to be used. Note that this arrangement assumes that tasks are not sent POSIX signals (or anything similar) from the time that the first task is spawned through core_initcall() time. Fixes: 8b355e3bc140 ("rcu: Drive expedited grace periods from workqueue") Reported-by: "Zheng, Lv" <lv.zheng@intel.com> Reported-by: Borislav Petkov <bp@alien8.de> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Tested-by: Stan Kain <stan.kain@gmail.com> Tested-by: Ivan <waffolz@hotmail.com> Tested-by: Emanuel Castelo <emanuel.castelo@gmail.com> Tested-by: Bruno Pesavento <bpesavento@infinito.it> Tested-by: Borislav Petkov <bp@suse.de> Tested-by: Frederic Bezies <fredbezies@gmail.com> Cc: <stable@vger.kernel.org> # 4.9.0-
Diffstat (limited to 'include/trace/events')