From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Subject: Re: [PATCH] selftests/ftrace: Exclude "(fault)" in testing add/remove eprobe events
Date: Wed, 8 Sep 2021 12:47:57 +0900 [thread overview]
Message-ID: <20210908124757.b80638d630436bebf1280836@kernel.org> (raw)
In-Reply-To: <20210907230429.5783d519@rorschach.local.home>
On Tue, 7 Sep 2021 23:04:29 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>
>
> The original test for adding and removing eprobes used synthetic events
> and retrieved the filename from the open system call at the end of the
> system call. This would allow it to always be loaded into the page tables
> when accessed.
>
> Masami suggested that the test was too complex for just testing add and
> remove, so it was changed to test just adding and removing an event probe
> on top of the start of the open system call event. Now it is possible that
> the filename will not be loaded into memory at the time the eprobe is
> triggered, and will result in "(fault)" being displayed in the event. This
> causes the test to fail.
>
> Account for "(fault)" also being one of the values of the filename field
> of the event probe.
Looks good to me.
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thank you,
>
> Fixes: 079db70794ec5 ("selftests/ftrace: Add test case to test adding and removing of event probe")
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
> .../selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc
> index 25a3da4eaa44..5f5b2ba3e557 100644
> --- a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc
> +++ b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_eprobe.tc
> @@ -22,7 +22,7 @@ ls
> echo 0 > events/eprobes/$EPROBE/enable
>
> content=`grep '^ *ls-' trace | grep 'file='`
> -nocontent=`grep '^ *ls-' trace | grep 'file=' | grep -v -e '"/' -e '"."'` || true
> +nocontent=`grep '^ *ls-' trace | grep 'file=' | grep -v -e '"/' -e '"."' -e '(fault)' ` || true
>
> if [ -z "$content" ]; then
> exit_fail
> --
> 2.31.1
>
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2021-09-08 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 3:04 Steven Rostedt
2021-09-08 3:47 ` 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=20210908124757.b80638d630436bebf1280836@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--cc=tz.stoyanov@gmail.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
all inboxes | Powered by JetHome®