Steven Rostedt (Google)
f3dc260cd5
tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
[ Upstream commit b55b0a0d7c ]
If a large event was added to the ring buffer that is larger than what the
trace_seq can handle, it just drops the output:
~# cat /sys/kernel/tracing/trace
# tracer: nop
#
# entries-in-buffer/entries-written: 2/2 #P:8
#
# _-----=> irqs-off/BH-disabled
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / _-=> migrate-disable
# |||| / delay
# TASK-PID CPU# ||||| TIMESTAMP FUNCTION
# | | | ||||| | |
<...>-859 [001] ..... 141.118951: tracing_mark_write <...>-859 [001] ..... 141.148201: tracing_mark_write: 78901234
Instead, catch this case and add some context:
~# cat /sys/kernel/tracing/trace
# tracer: nop
#
# entries-in-buffer/entries-written: 2/2 #P:8
#
# _-----=> irqs-off/BH-disabled
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / _-=> migrate-disable
# |||| / delay
# TASK-PID CPU# ||||| TIMESTAMP FUNCTION
# | | | ||||| | |
<...>-852 [001] ..... 121.550551: tracing_mark_write[LINE TOO BIG]
<...>-852 [001] ..... 121.550581: tracing_mark_write: 78901234
This now emulates the same output as trace_pipe.
Link: https://lore.kernel.org/linux-trace-kernel/20231209171058.78c1a026@gandalf.local.home
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Reviewed-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2024-01-20 11:51:43 +01:00
..
2023-04-28 16:11:26 -07:00
2023-02-21 09:23:22 -07:00
2023-09-15 10:32:40 -07:00
2023-07-12 12:06:04 -04:00
2023-10-17 10:22:42 +09:00
2023-07-12 12:06:04 -04:00
2024-01-05 15:19:44 +01:00
2023-06-30 10:44:53 -07:00
2023-03-19 12:20:48 -04:00
2023-08-23 09:39:45 +09:00
2022-04-26 17:58:50 -04:00
2021-10-05 17:38:45 -04:00
2023-12-13 18:45:19 +01:00
2022-11-23 19:08:30 -05:00
2024-01-05 15:19:44 +01:00
2024-01-01 12:42:45 +00:00
2022-09-26 13:01:09 -04:00
2022-09-26 13:01:09 -04:00
2023-07-05 10:30:49 -04:00
2023-08-23 09:40:16 +09:00
2023-08-23 09:40:16 +09:00
2022-11-23 19:07:12 -05:00
2023-07-30 18:11:44 -04:00
2023-08-23 09:39:15 +09:00
2022-11-23 19:08:31 -05:00
2023-11-08 11:56:21 +01:00
2023-07-23 11:18:52 -04:00
2023-09-07 16:38:54 -04:00
2023-11-28 17:20:05 +00:00
2023-07-28 19:59:03 -04:00
2023-09-30 16:25:41 -04:00
2023-11-08 11:56:21 +01:00
2023-07-30 18:11:44 -04:00
2023-11-28 17:20:13 +00:00
2023-06-20 18:38:37 -04:00
2021-10-27 11:21:49 -04:00
2023-09-01 21:00:00 -04:00
2023-08-17 13:49:37 -04:00
2023-07-12 12:06:04 -04:00
2023-11-20 11:59:38 +01:00
2023-06-22 10:39:56 -04:00
2023-06-30 10:33:17 -07:00
2023-03-29 06:52:08 -04:00
2023-01-31 15:01:46 +01:00
2021-10-08 18:08:43 -04:00
2023-07-14 17:04:58 +09:00
2023-07-14 17:04:58 +09:00
2023-08-23 09:41:13 +09:00
2023-10-20 22:10:41 +09:00
2022-05-26 21:12:52 -04:00
2022-05-12 00:37:11 +02:00
2023-08-17 13:49:37 -04:00
2023-05-28 21:15:46 -04:00
2023-07-28 19:59:04 -04:00
2021-10-08 18:08:43 -04:00
2021-10-08 18:08:43 -04:00
2023-01-25 10:31:24 -05:00
2023-08-01 10:53:28 -07:00
2023-09-02 11:10:50 -07:00
2024-01-20 11:51:43 +01:00
2023-11-08 11:56:21 +01:00
2022-10-03 12:20:31 -04:00
2023-07-23 11:08:14 -04:00