diff options
| author |   Tom Zanussi <zanussi@kernel.org> | 2020-02-14 16:56:38 -0600 |
|---|---|---|
| committer |   Steven Rostedt (VMware) <rostedt@goodmis.org> | 2020-02-20 16:24:17 -0500 |
| commit | 279eef0531928a6669230879a6eed081513ad5a3 (patch) | |
| tree | 149c8e4b87e1bd5ab4d641b15d135b6ae17e2a38 /kernel/Kconfig.locks | |
| parent | tracing: Consolidate trace() functions (diff) | |
| download | wireguard-linux-279eef0531928a6669230879a6eed081513ad5a3.tar.xz wireguard-linux-279eef0531928a6669230879a6eed081513ad5a3.zip | |
tracing: Make sure synth_event_trace() example always uses u64
synth_event_trace() is the varargs version of synth_event_trace_array(),
which takes an array of u64, as do synth_event_add_val() et al.
To not only be consistent with those, but also to address the fact
that synth_event_trace() expects every arg to be of the same type
since it doesn't also pass in e.g. a format string, the caller needs
to make sure all args are of the same type, u64. u64 is used because
it needs to accomodate the largest type available in synthetic events,
which is u64.
This fixes the bug reported by the kernel test robot/Rong Chen.
Link: https://lore.kernel.org/lkml/20200212113444.GS12867@shao2-debian/
Link: http://lkml.kernel.org/r/894c4e955558b521210ee0642ba194a9e603354c.1581720155.git.zanussi@kernel.org
Fixes: 9fe41efaca084 ("tracing: Add synth event generation test module")
Reported-by: kernel test robot <rong.a.chen@intel.com>
Signed-off-by: Tom Zanussi <zanussi@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'kernel/Kconfig.locks')
0 files changed, 0 insertions, 0 deletions