rcu: Turn off tracing before dumping trace
Currently, RCU allows tracing to continue when it automatically does ftrace_dump() after detecting an error condition, which can result in excessively large traces and lost trace events. This commit therefore does a tracing_off() before any of these ftrace_dump() calls. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
This commit is contained in:
@@ -220,8 +220,10 @@ do { \
|
|||||||
static atomic_t ___rfd_beenhere = ATOMIC_INIT(0); \
|
static atomic_t ___rfd_beenhere = ATOMIC_INIT(0); \
|
||||||
\
|
\
|
||||||
if (!atomic_read(&___rfd_beenhere) && \
|
if (!atomic_read(&___rfd_beenhere) && \
|
||||||
!atomic_xchg(&___rfd_beenhere, 1)) \
|
!atomic_xchg(&___rfd_beenhere, 1)) { \
|
||||||
|
tracing_off(); \
|
||||||
ftrace_dump(oops_dump_mode); \
|
ftrace_dump(oops_dump_mode); \
|
||||||
|
} \
|
||||||
} while (0)
|
} while (0)
|
||||||
|
|
||||||
void rcu_early_boot_tests(void);
|
void rcu_early_boot_tests(void);
|
||||||
|
|||||||
Reference in New Issue
Block a user