summaryrefslogtreecommitdiffstats
path: root/lib/test_fortify/write_overflow-strncpy-src.c
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2021-08-06 08:57:26 -0700
committerPaul E. McKenney <paulmck@kernel.org>2021-09-13 16:36:16 -0700
commitfd13fe16db0d82612b260640f4e26f6d9d1e11fd (patch)
treeca0266ea052c516cc2634505d08aae99cffa3c91 /lib/test_fortify/write_overflow-strncpy-src.c
parenteb77abfdeed29dd032c923e16fe8d91fa95cd316 (diff)
downloadlinux-fd13fe16db0d82612b260640f4e26f6d9d1e11fd.tar.gz
linux-fd13fe16db0d82612b260640f4e26f6d9d1e11fd.tar.bz2
linux-fd13fe16db0d82612b260640f4e26f6d9d1e11fd.zip
rcutorture: Don't cpuhp_remove_state() if cpuhp_setup_state() failed
Currently, in CONFIG_RCU_BOOST kernels, if the rcu_torture_init() function's call to cpuhp_setup_state() fails, rcu_torture_cleanup() gamely passes nonsense to cpuhp_remove_state(). This results in strange and misleading splats. This commit therefore ensures that if the rcu_torture_init() function's call to cpuhp_setup_state() fails, rcu_torture_cleanup() avoids invoking cpuhp_remove_state(). 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