tracing: Don't display trigger file for events that can't be enabled
authorChunyu Hu <chuhu@redhat.com>
Tue, 3 May 2016 11:34:34 +0000 (19:34 +0800)
committerBen Hutchings <ben@decadent.org.uk>
Wed, 15 Jun 2016 20:29:30 +0000 (21:29 +0100)
commit543320c210c85697272ed34d8e1b2b910521d26e
tree4a15c1a63ed579a6a6f6a27b36fdb193374ba2a0
parent475d831dbd86b89657c3a9d93b9a8e9912ce6d7e
tracing: Don't display trigger file for events that can't be enabled

commit 854145e0a8e9a05f7366d240e2f99d9c1ca6d6dd upstream.

Currently register functions for events will be called
through the 'reg' field of event class directly without
any check when seting up triggers.

Triggers for events that don't support register through
debug fs (events under events/ftrace are for trace-cmd to
read event format, and most of them don't have a register
function except events/ftrace/functionx) can't be enabled
at all, and an oops will be hit when setting up trigger
for those events, so just not creating them is an easy way
to avoid the oops.

Link: http://lkml.kernel.org/r/1462275274-3911-1-git-send-email-chuhu@redhat.com
Fixes: 85f2b08268c01 ("tracing: Add basic event trigger framework")
Signed-off-by: Chunyu Hu <chuhu@redhat.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
kernel/trace/trace_events.c