ftrace/selftest: make unresolved cases cause failure if --fail-unresolved set
authorAlan Maguire <alan.maguire@oracle.com>
Wed, 19 Feb 2020 09:33:30 +0000 (09:33 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 27 May 2020 15:46:33 +0000 (17:46 +0200)
commit1ae9f1a62a5093458ab905e8e3cc1836467440c3
treef6e8e056cf1c1e90af7dc9974dffc483aa33455d
parent2eac9d3dc23ff5e942e5d685272b74bc436279a2
ftrace/selftest: make unresolved cases cause failure if --fail-unresolved set

[ Upstream commit b730d668138cb3dd9ce78f8003986d1adae5523a ]

Currently, ftracetest will return 1 (failure) if any unresolved cases
are encountered.  The unresolved status results from modules and
programs not being available, and as such does not indicate any
issues with ftrace itself.  As such, change the behaviour of
ftracetest in line with unsupported cases; if unsupported cases
happen, ftracetest still returns 0 unless --fail-unsupported.  Here
--fail-unresolved is added and the default is to return 0 if
unresolved results occur.

Signed-off-by: Alan Maguire <alan.maguire@oracle.com>
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
tools/testing/selftests/ftrace/ftracetest