diff options
| author | Steven Rostedt <rostedt@goodmis.org> | 2026-03-23 20:22:12 -0400 |
|---|---|---|
| committer | Steven Rostedt (Google) <rostedt@goodmis.org> | 2026-03-24 22:21:15 -0400 |
| commit | 23d1cfc0216e28140cb0c914814c03d127a3ad6e (patch) | |
| tree | 833a9448f7d76be75be44250272f75e086c27013 /rust/kernel/interop/git@git.tavy.me:linux-stable.git | |
| parent | dc1d9408c961c1c4d4b3b99a1d9390c17e13de71 (diff) | |
ring-buffer: Show what clock function is used on timestamp errors
The testing for tracing was triggering a timestamp count issue that was
always off by one. This has been happening for some time but has never
been reported by anyone else. It was finally discovered to be an issue
with the "uptime" (jiffies) clock that happened to be traced and the
internal recursion caused the discrepancy. This would have been much
easier to solve if the clock function being used was displayed when the
error was detected.
Add the clock function to the error output.
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Link: https://patch.msgid.link/20260323202212.479bb288@gandalf.local.home
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Diffstat (limited to 'rust/kernel/interop/git@git.tavy.me:linux-stable.git')
0 files changed, 0 insertions, 0 deletions