From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: <shuah@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>, <mingo@redhat.com>,
<ice_yangxiao@163.com>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH] selftests/ftrace: Check the first record for kprobe_args_type.tc
Date: Wed, 15 Apr 2020 09:19:23 +0800 [thread overview]
Message-ID: <5E96611B.10100@cn.fujitsu.com> (raw)
In-Reply-To: <20200408003026.24627a881c8f1eacb01cea48@kernel.org>
Hi Shuah,
Sorry to bother you.
Steven and Masami have reviewed this patch so can you apply it to your
tree?
Thanks,
Xiao Yang
On 2020/4/7 23:30, Masami Hiramatsu wrote:
> On Tue, 7 Apr 2020 09:54:00 -0400
> Steven Rostedt<rostedt@goodmis.org> wrote:
>
>> On Tue, 7 Apr 2020 14:34:19 +0800
>> Xiao Yang<yangx.jy@cn.fujitsu.com> wrote:
>>
>>> It is possible to get multiple records from trace during test and then more
>>> than 4 arguments are assigned to ARGS. This situation results in the failure
>>> of kprobe_args_type.tc. For example:
>>> -----------------------------------------------------------
>>> grep testprobe trace
>>> ftracetest-5902 [001] d... 111195.682227: testprobe: (_do_fork+0x0/0x460) arg1=334823024 arg2=334823024 arg3=0x13f4fe70 arg4=7
>>> pmlogger-5949 [000] d... 111195.709898: testprobe: (_do_fork+0x0/0x460) arg1=345308784 arg2=345308784 arg3=0x1494fe70 arg4=7
>>> grep testprobe trace
>>> sed -e 's/.* arg1=\(.*\) arg2=\(.*\) arg3=\(.*\) arg4=\(.*\)/\1 \2 \3 \4/'
>>> ARGS='334823024 334823024 0x13f4fe70 7
>>> 345308784 345308784 0x1494fe70 7'
>>> -----------------------------------------------------------
>>>
>>> We don't care which process calls do_fork so just check the first record to
>>> fix the issue.
>>
>> Looks good to me, but Masami will need to ack it.
>>
>
> Ah, good catch! I had fixed similar issue but missed this one.
>
> Acked-by: Masami Hiramatsu<mhiramat@kernel.org>
>
> Thank you!
>
>> -- Steve
>>
>>>
>>> Signed-off-by: Xiao Yang<yangx.jy@cn.fujitsu.com>
>>> ---
>>> .../testing/selftests/ftrace/test.d/kprobe/kprobe_args_type.tc | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_type.tc b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_type.tc
>>> index 1bcb67dcae26..81490ecaaa92 100644
>>> --- a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_type.tc
>>> +++ b/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_args_type.tc
>>> @@ -38,7 +38,7 @@ for width in 64 32 16 8; do
>>> echo 0> events/kprobes/testprobe/enable
>>>
>>> : "Confirm the arguments is recorded in given types correctly"
>>> - ARGS=`grep "testprobe" trace | sed -e 's/.* arg1=\(.*\) arg2=\(.*\) arg3=\(.*\) arg4=\(.*\)/\1 \2 \3 \4/'`
>>> + ARGS=`grep "testprobe" trace | head -n 1 | sed -e 's/.* arg1=\(.*\) arg2=\(.*\) arg3=\(.*\) arg4=\(.*\)/\1 \2 \3 \4/'`
>>> check_types $ARGS $width
>>>
>>> : "Clear event for next loop"
>>
>
>
next prev parent reply other threads:[~2020-04-15 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 6:34 [PATCH] selftests/ftrace: Check the first record for kprobe_args_type.tc Xiao Yang
2020-04-07 13:54 ` Steven Rostedt
2020-04-07 15:30 ` Masami Hiramatsu
2020-04-15 1:19 ` Xiao Yang [this message]
2020-04-24 1:12 ` Xiao Yang
2020-04-24 1:18 ` Steven Rostedt
2020-04-24 1:36 ` Xiao Yang
2020-04-24 12:22 ` Shuah Khan
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=5E96611B.10100@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=ice_yangxiao@163.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.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