From: Steven Rostedt (VMware) Date: Thu, 10 May 2018 16:40:21 +0000 (-0400) Subject: tracing: Prevent further users of zero size static arrays in trace events X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=4a0772cf0674346f3c1ff1043e440523b7e3131b;p=linux.git tracing: Prevent further users of zero size static arrays in trace events A zero size static array has special meaning in the ftrace infrastructure. Trace events are for recording data in the trace buffers that is normally difficult to obtain via probes or function tracing. There is no reason for any trace event to declare a zero size static array. If one does, BUILD_BUG_ON() will trigger and prevent the kernel from compiling. Reviewed-by: Namhyung Kim Signed-off-by: Steven Rostedt (VMware) --- diff --git a/include/trace/trace_events.h b/include/trace/trace_events.h index bfda803b0a093..4ecdfe2e35800 100644 --- a/include/trace/trace_events.h +++ b/include/trace/trace_events.h @@ -422,6 +422,7 @@ static struct trace_event_functions trace_event_type_funcs_##call = { \ do { \ char *type_str = #type"["__stringify(len)"]"; \ BUILD_BUG_ON(len > MAX_FILTER_STR_VAL); \ + BUILD_BUG_ON(len <= 0); \ ret = trace_define_field(event_call, type_str, #item, \ offsetof(typeof(field), item), \ sizeof(field.item), \