diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-08-17 09:47:18 -1000 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-08-17 09:47:18 -1000 |
commit | 614cb2751d3150850d459bee596c397f344a7936 (patch) | |
tree | 1f1903908a6f90b49c80614e12f3e55507ee03f0 /kernel/configs.c | |
parent | 794c7931a2428a656551f2179e6a093233a6e0aa (diff) | |
parent | 6c34df6f350df9579ce99d887a2b5fa14cc13b32 (diff) |
Merge tag 'trace-v5.14-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull tracing fix from Steven Rostedt:
"Limit the shooting in the foot of tp_printk
The "tp_printk" option redirects the trace event output to printk at
boot up. This is useful when a machine crashes before boot where the
trace events can not be retrieved by the in kernel ring buffer. But it
can be "dangerous" because trace events can be located in high
frequency locations such as interrupts and the scheduler, where a
printk can slow it down that it live locks the machine (because by the
time the printk finishes, the next event is triggered). Thus tp_printk
must be used with care.
It was discovered that the filter logic to trace events does not apply
to the tp_printk events. This can cause a surprise and live lock when
the user expects it to be filtered to limit the amount of events
printed to the console when in fact it still prints everything"
* tag 'trace-v5.14-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
tracing: Apply trace filters on all output channels
Diffstat (limited to 'kernel/configs.c')
0 files changed, 0 insertions, 0 deletions