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)
committerSasha Levin <sasha.levin@oracle.com>
Tue, 17 May 2016 17:42:56 +0000 (13:42 -0400)
commit3216eb22857e515aa89f594f84c0ef2a36a59b08
tree34662aa7b071ad615ecd342b37f57f4776291b96
parent9abc9e72c77166342589d02fb7c0dcabe78d9358
tracing: Don't display trigger file for events that can't be enabled

[ Upstream commit 854145e0a8e9a05f7366d240e2f99d9c1ca6d6dd ]

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
Cc: stable@vger.kernel.org # 3.14+
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: Sasha Levin <sasha.levin@oracle.com>
kernel/trace/trace_events.c