| commit | 4a0772cf0674346f3c1ff1043e440523b7e3131b | |
| author | Steven Rostedt (VMware) <rostedt@goodmis.org> | |
| Thu, 10 May 2018 16:40:21 +0000 (10 12:40 -0400) | ||
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | |
| Tue, 29 May 2018 12:29:13 +0000 (29 08:29 -0400) | ||
| tree | 671556af17697d8aca4e28fc7de0e74c9109a924 | treesnapshot (tar.gz zip) |
| parent | 10f20e9f9da943426382da3d4947ea46fa1db492 | commitdiff |
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 <namhyung@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
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 <namhyung@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
| include/trace/trace_events.h | diffblobblamehistory |