diff options
author | 2022-04-11 17:19:03 +0200 | |
---|---|---|
committer | 2022-06-21 15:55:02 -0700 | |
commit | 14c0017c19ead104511dbcf6a59b83b2456d09af (patch) | |
tree | 0328213c34709ec8df723cb771b23cccb27cbc4c /scripts/generate_rust_analyzer.py | |
parent | torture: Make kvm-remote.sh announce which system is being waited on (diff) | |
download | wireguard-linux-14c0017c19ead104511dbcf6a59b83b2456d09af.tar.xz wireguard-linux-14c0017c19ead104511dbcf6a59b83b2456d09af.zip |
rcu/torture: Change order of warning and trace dump
Dumping a big ftrace buffer could lead to a RCU stall. So there is the
ftrace buffer and the stall information which needs to be printed. When
there is additionally a WARN_ON() which describes the reason for the ftrace
buffer dump and the WARN_ON() is executed _after_ ftrace buffer dump, the
information get lost in the middle of the RCU stall information.
Therefore print WARN_ON() message before dumping the ftrace buffer in
rcu_torture_writer().
[ paulmck: Add tracing_off() to avoid cruft from WARN(). ]
Signed-off-by: Anna-Maria Behnsen <anna-maria@linutronix.de>
Reviewed-by: Benedikt Spranger <b.spranger@linutronix.de>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions