From: Shuah Khan <skhan@linuxfoundation.org>
To: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuah@kernel.org>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] selftests/ftrace: Return unsupported if no error_log file
Date: Thu, 28 May 2020 10:45:55 -0600 [thread overview]
Message-ID: <bfaf034d-4bbb-1ca2-1cd7-309d4df79403@linuxfoundation.org> (raw)
In-Reply-To: <159040205682.10129.10826221002090446642.stgit@devnote2>
On 5/25/20 4:20 AM, Masami Hiramatsu wrote:
> Check whether error_log file exists in tracing/error_log testcase
> and return UNSUPPORTED if no error_log file.
>
> This can happen if we run the ftracetest on the older stable
> kernel.
>
> Fixes: 4eab1cc461a6 ("selftests/ftrace: Add tracing/error_log testcase")
> Cc: stable@vger.kernel.org
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> ---
> .../ftrace/test.d/ftrace/tracing-error-log.tc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/testing/selftests/ftrace/test.d/ftrace/tracing-error-log.tc b/tools/testing/selftests/ftrace/test.d/ftrace/tracing-error-log.tc
> index 021c03fd885d..23465823532b 100644
> --- a/tools/testing/selftests/ftrace/test.d/ftrace/tracing-error-log.tc
> +++ b/tools/testing/selftests/ftrace/test.d/ftrace/tracing-error-log.tc
> @@ -14,6 +14,8 @@ if [ ! -f set_event ]; then
> exit_unsupported
> fi
>
> +[ -f error_log ] || exit_unsupported
> +
> ftrace_errlog_check 'event filter parse error' '((sig >= 10 && sig < 15) || dsig ^== 17) && comm != bash' 'events/signal/signal_generate/filter'
>
> exit 0
>
Applied to
git.kernel.org/pub/scm/linux/kernel/git/shuah/linux kselftest.git/ next
branch for Linux 5.8-rc1
thanks,
-- Shuah
prev parent reply other threads:[~2020-05-28 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 10:20 [PATCH] selftests/ftrace: Return unsupported if no error_log file Masami Hiramatsu
2020-05-28 16:45 ` Shuah Khan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bfaf034d-4bbb-1ca2-1cd7-309d4df79403@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tom.zanussi@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.