tracing: Have TRACE_DEFINE_ENUM affect trace event types as well
authorSteven Rostedt (Google) <rostedt@goodmis.org>
Fri, 11 Mar 2022 04:27:38 +0000 (23:27 -0500)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Fri, 11 Mar 2022 16:49:24 +0000 (11:49 -0500)
commitb3bc8547d3be60898818885f5bf22d0a62e2eb48
tree3ed25a4e5deda96b5ee94476e1990f2da756f4f9
parent9f438d4d7fa2f59570cd58bca24ac82e7172d63b
tracing: Have TRACE_DEFINE_ENUM affect trace event types as well

The macro TRACE_DEFINE_ENUM is used to convert enums in the kernel to
their actual value when they are exported to user space via the trace
event format file.

Currently only the enums in the "print fmt" (TP_printk in the TRACE_EVENT
macro) have the enums converted. But the enums can be used to denote array
size:

        field:unsigned int fc_ineligible_rc[EXT4_FC_REASON_MAX]; offset:12;      size:36;        signed:0;

The EXT4_FC_REASON_MAX has no meaning to userspace but it needs to know
that information to know how to parse the array.

Have the array indexes also be parsed as well.

Link: https://lore.kernel.org/all/cover.1646922487.git.riteshh@linux.ibm.com/
Reported-by: Ritesh Harjani <riteshh@linux.ibm.com>
Tested-by: Ritesh Harjani <riteshh@linux.ibm.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
kernel/trace/trace_events.c