From: Masami Hiramatsu <mhiramat@kernel.org>
To: shuah@kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Rajvi Jingar <rajvi.jingar@intel.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH] selftests/ftrace: Introduce exit_pass and exit_fail
Date: Sat, 4 Nov 2017 04:34:33 +0900 [thread overview]
Message-ID: <20171104043433.d3a9212548d5c5e2f1ffe4fc@kernel.org> (raw)
In-Reply-To: <02195d89-7999-0983-52bf-a0d222e69b38@kernel.org>
On Wed, 1 Nov 2017 15:18:41 -0600
Shuah Khan <shuah@kernel.org> wrote:
> On 10/31/2017 10:23 PM, Masami Hiramatsu wrote:
> > On Tue, 31 Oct 2017 17:44:32 -0400
> > Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> >> On Tue, 31 Oct 2017 23:51:42 +0900
> >> Masami Hiramatsu <mhiramat@kernel.org> wrote:
> >>
> >>> diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/busy_check.tc b/tools/testing/selftests/ftrace/test.d/kprobe/busy_check.tc
> >>> index 74507db8bbc8..b8701fa0b8f2 100644
> >>> --- a/tools/testing/selftests/ftrace/test.d/kprobe/busy_check.tc
> >>> +++ b/tools/testing/selftests/ftrace/test.d/kprobe/busy_check.tc
> >>> @@ -8,7 +8,7 @@ echo > kprobe_events
> >>> echo p:myevent _do_fork > kprobe_events
> >>> test -d events/kprobes/myevent
> >>> echo 1 > events/kprobes/myevent/enable
> >>> -echo > kprobe_events && exit 1 # this must fail
> >>> +echo > kprobe_events && exit_fail
> >>
> >> Should we keep the comment about "this must fail", otherwise it may
> >> look like a mistake. Echoing in kprobe_events returns failure here?
> >
> > Ah, good catch! I misread the comment is for "exit 1"...
> >
> > Thank you,
> >
> >>
> >> -- Steve
> >>
> >>
> >>> echo 0 > events/kprobes/myevent/enable
> >>> echo > kprobe_events # this must succeed
> >>> clear_trace
> >
> >
>
> Hi Masami,
>
> Thanks Steve for the catch. I will wait for v2 then.
Sorry for later, I'll send it soon.
Thank you,
>
> thanks,
> -- Shuah
>
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2017-11-03 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 14:51 Masami Hiramatsu
2017-10-31 21:44 ` Steven Rostedt
2017-11-01 4:23 ` Masami Hiramatsu
2017-11-01 21:18 ` Shuah Khan
2017-11-03 19:34 ` Masami Hiramatsu [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=20171104043433.d3a9212548d5c5e2f1ffe4fc@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rajvi.jingar@intel.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome