diff options
| author | Paul E. McKenney <paulmck@kernel.org> | 2021-08-05 13:28:24 -0700 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2021-09-13 16:36:16 -0700 |
| commit | efeff6b39b9de4480572c7b0c5eb77204795cb57 (patch) | |
| tree | c039b31ab10219accfb5ca1c93b01596d5a84f5c /lib/test_fortify/write_overflow-strscpy.c | |
| parent | fda84866b1e68ab409074e7fcf1a7db800615445 (diff) | |
| download | linux-efeff6b39b9de4480572c7b0c5eb77204795cb57.tar.gz linux-efeff6b39b9de4480572c7b0c5eb77204795cb57.tar.bz2 linux-efeff6b39b9de4480572c7b0c5eb77204795cb57.zip | |
rcutorture: Warn on individual rcu_torture_init() error conditions
When running rcutorture as a module, any rcu_torture_init() issues will be
reflected in the error code from modprobe or insmod, as the case may be.
However, these error codes are not available when running rcutorture
built-in, for example, when using the kvm.sh script. This commit
therefore adds WARN_ON_ONCE() to allow distinguishing rcu_torture_init()
errors when running rcutorture built-in.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'lib/test_fortify/write_overflow-strscpy.c')
0 files changed, 0 insertions, 0 deletions