linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Francis Deslauriers <francis.deslauriers@efficios.com>,
	peterz@infradead.org, mathieu.desnoyers@efficios.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] selftests/ftrace: Fix kprobe string testcase to not probe notrace function
Date: Sat, 28 Jul 2018 08:59:22 +0900	[thread overview]
Message-ID: <20180728085922.bbc1ff641f27d59ae8c02ef2@kernel.org> (raw)
In-Reply-To: <20180727174307.33990e4f@gandalf.local.home>

On Fri, 27 Jul 2018 17:43:07 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Thu, 26 Jul 2018 14:54:23 +0900
> Masami Hiramatsu <mhiramat@kernel.org> wrote:
> 
> > Fix kprobe string argument testcase to not probe notrace
> > function. Instead, it probes tracefs function which must
> > be available with ftrace.
> 
> Hi Masami,
> 
> With these patches applied, this test fails:
> 
>  ./ftracetest  test.d/kprobe/probepoint.tc
> 
> Gives me the error in dmseg:
> 
>   trace_kprobe: Could not probe notrace function create_trace_kprobe
> 
> Is this expected? I don't see create_trace_kprobe as a notrace function
> either.
> 
> I even applied patch 3 (going through Shuah's tree) to me test and it
> still fails.

Oops, why I missed this...
OK, I'll fix it.

Thanks,

> 
> Config attached.
> 
> -- Steve
> 
> > 
> > Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> > ---
> >  .../ftrace/test.d/kprobe/kprobe_args_string.tc     |   30 ++++++++------------
> >  1 file changed, 12 insertions(+), 18 deletions(-)
> > 
> > diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_string.tc b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_string.tc
> > index a0002563e9ee..1ad70cdaf442 100644
> > --- a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_string.tc
> > +++ b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_string.tc
> > @@ -9,28 +9,22 @@ echo > kprobe_events
> >  
> >  case `uname -m` in
> >  x86_64)
> > -  ARG2=%si
> > -  OFFS=8
> > +  ARG1=%di
> >  ;;
> >  i[3456]86)
> > -  ARG2=%cx
> > -  OFFS=4
> > +  ARG1=%ax
> >  ;;
> >  aarch64)
> > -  ARG2=%x1
> > -  OFFS=8
> > +  ARG1=%x0
> >  ;;
> >  arm*)
> > -  ARG2=%r1
> > -  OFFS=4
> > +  ARG1=%r0
> >  ;;
> >  ppc64*)
> > -  ARG2=%r4
> > -  OFFS=8
> > +  ARG1=%r3
> >  ;;
> >  ppc*)
> > -  ARG2=%r4
> > -  OFFS=4
> > +  ARG1=%r3
> >  ;;
> >  *)
> >    echo "Please implement other architecture here"
> > @@ -38,17 +32,17 @@ ppc*)
> >  esac
> >  
> >  : "Test get argument (1)"
> > -echo "p:testprobe create_trace_kprobe arg1=+0(+0(${ARG2})):string" > kprobe_events
> > +echo "p:testprobe tracefs_create_dir arg1=+0(${ARG1}):string" > kprobe_events
> >  echo 1 > events/kprobes/testprobe/enable
> > -! echo test >> kprobe_events
> > -tail -n 1 trace | grep -qe "testprobe.* arg1=\"test\""
> > +echo "p:test _do_fork" >> kprobe_events
> > +grep -qe "testprobe.* arg1=\"test\"" trace
> >  
> >  echo 0 > events/kprobes/testprobe/enable
> >  : "Test get argument (2)"
> > -echo "p:testprobe create_trace_kprobe arg1=+0(+0(${ARG2})):string arg2=+0(+${OFFS}(${ARG2})):string" > kprobe_events
> > +echo "p:testprobe tracefs_create_dir arg1=+0(${ARG1}):string arg2=+0(${ARG1}):string" > kprobe_events
> >  echo 1 > events/kprobes/testprobe/enable
> > -! echo test1 test2 >> kprobe_events
> > -tail -n 1 trace | grep -qe "testprobe.* arg1=\"test1\" arg2=\"test2\""
> > +echo "p:test _do_fork" >> kprobe_events
> > +grep -qe "testprobe.* arg1=\"test\" arg2=\"test\"" trace
> >  
> >  echo 0 > events/enable
> >  echo > kprobe_events
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

      reply	other threads:[~2018-07-27 23:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26  5:52 [PATCH v2 0/3] tracing: kprobes: Prohibit probing on notrace functions Masami Hiramatsu
2018-07-26  5:53 ` [PATCH v2 1/3] tracing: kprobes: Prohibit probing on notrace function Masami Hiramatsu
2018-07-28  1:00   ` Masami Hiramatsu
2018-07-28  8:11   ` kbuild test robot
2018-07-28 13:42     ` Masami Hiramatsu
2018-07-28  8:24   ` kbuild test robot
2018-07-26  5:53 ` [PATCH v2 2/3] selftest/ftrace: Move kprobe selftest function to separate compile unit Masami Hiramatsu
2018-07-26 23:29   ` Steven Rostedt
2018-07-27 12:39     ` Masami Hiramatsu
2018-07-27 12:44     ` [PATCH v2.1 " Masami Hiramatsu
2018-07-26  5:54 ` [PATCH v2 3/3] selftests/ftrace: Fix kprobe string testcase to not probe notrace function Masami Hiramatsu
2018-07-26  7:44   ` Masami Hiramatsu
2018-07-26 19:58     ` Steven Rostedt
2018-07-26 21:22       ` Shuah Khan
2018-07-27 12:47         ` Masami Hiramatsu
2018-07-27 14:26           ` Shuah Khan
2018-07-27 14:31             ` Steven Rostedt
2018-07-28  2:24               ` Masami Hiramatsu
2018-07-27 21:43   ` Steven Rostedt
2018-07-27 23:59     ` 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=20180728085922.bbc1ff641f27d59ae8c02ef2@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=francis.deslauriers@efficios.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    /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;
as well as URLs for NNTP newsgroup(s).