diff options
| author | Juri Lelli <juri.lelli@redhat.com> | 2021-08-10 10:48:15 +0200 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2021-09-13 16:32:46 -0700 |
| commit | ebb6d30d9ed1fe7137486e1be2ae9d621e918c4a (patch) | |
| tree | 8410a44321e9f576f68d2363aab8040ce53223a6 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 4aa846f97c0c0d9740d120f9ac3e2fba1522ac0c (diff) | |
| download | linux-ebb6d30d9ed1fe7137486e1be2ae9d621e918c4a.tar.gz linux-ebb6d30d9ed1fe7137486e1be2ae9d621e918c4a.tar.bz2 linux-ebb6d30d9ed1fe7137486e1be2ae9d621e918c4a.zip | |
rcu: Make rcu_normal_after_boot writable again
Certain configurations (e.g., systems that make heavy use of netns)
need to use synchronize_rcu_expedited() to service RCU grace periods
even after boot.
Even though synchronize_rcu_expedited() has been traditionally
considered harmful for RT for the heavy use of IPIs, it is perfectly
usable under certain conditions (e.g. nohz_full).
Make rcupdate.rcu_normal_after_boot= again writeable on RT (if NO_HZ_
FULL is defined), but keep its default value to 1 (enabled) to avoid
regressions. Users who need synchronize_rcu_expedited() will boot with
rcupdate.rcu_normal_after_ boot=0 in the kernel cmdline.
Reflect the change in synchronize_rcu_expedited_wait() by removing the
WARN related to CONFIG_PREEMPT_RT.
Signed-off-by: Juri Lelli <juri.lelli@redhat.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions