]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
tracing: Have syscall trace events show "0x" for values greater than 10
authorSteven Rostedt <rostedt@goodmis.org>
Tue, 23 Sep 2025 13:04:59 +0000 (09:04 -0400)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Tue, 23 Sep 2025 13:29:29 +0000 (09:29 -0400)
commit3add2d34bdfb1caab1d3f28ba0160f52dcff9353
tree2bc178f743af393f1cc3f27950fe90bedd645b2c
parent17a1a107d0e96c1b7eef875de46f1d953c557f88
tracing: Have syscall trace events show "0x" for values greater than 10

Currently the syscall trace events show each value as hexadecimal, but
without adding "0x" it can be confusing:

   sys_write(fd: 4, buf: 0x55c4a1fa9270, count: 44)

Looks like the above write wrote 44 bytes, when in reality it wrote 68
bytes.

Add a "0x" for all values greater or equal to 10 to remove the ambiguity.
For values less than 10, leave off the "0x" as that just adds noise to the
output.

Also change the iterator to check if "i" is nonzero and print the ", "
delimiter at the start, then adding the logic to the trace_seq_printf() at
the end.

Cc: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Namhyung Kim <namhyung@kernel.org>
Cc: Takaya Saeki <takayas@google.com>
Cc: Tom Zanussi <zanussi@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ian Rogers <irogers@google.com>
Cc: Douglas Raillard <douglas.raillard@arm.com>
Link: https://lore.kernel.org/20250923130713.764558957@kernel.org
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
kernel/trace/trace_syscalls.c