diff options
author | Axel Rasmussen <axelrasmussen@google.com> | 2020-10-10 01:05:23 +0300 |
---|---|---|
committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2020-10-15 19:01:14 +0300 |
commit | 6107742d15832011cd0396d821f3225b52551f1f (patch) | |
tree | 3a4e9b08918430a366a89ccf92bcc44492ceea44 /security/integrity/ima/ima_appraise.c | |
parent | 81ff92a93d954efa29e1d514934d6a47cd5f4558 (diff) | |
download | linux-6107742d15832011cd0396d821f3225b52551f1f.tar.xz |
tracing: support "bool" type in synthetic trace events
It's common [1] to define tracepoint fields as "bool" when they contain
a true / false value. Currently, defining a synthetic event with a
"bool" field yields EINVAL. It's possible to work around this by using
e.g. u8 (assuming sizeof(bool) is 1, and bool is unsigned; if either of
these properties don't match, you get EINVAL [2]).
Supporting "bool" explicitly makes hooking this up easier and more
portable for userspace.
[1]: grep -r "bool" include/trace/events/
[2]: check_synth_field() in kernel/trace/trace_events_hist.c
Link: https://lkml.kernel.org/r/20201009220524.485102-2-axelrasmussen@google.com
Acked-by: Michel Lespinasse <walken@google.com>
Acked-by: David Rientjes <rientjes@google.com>
Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'security/integrity/ima/ima_appraise.c')
0 files changed, 0 insertions, 0 deletions