From: Steven Rostedt <rostedt@goodmis.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: zhengyejian1@huawei.com, akaher@vmware.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, mhiramat@kernel.org,
shuah@kernel.org, skhan@linuxfoundation.org,
yeweihua4@huawei.com
Subject: Re: "[PATCH] selftests/ftrace: Correctly enable event in instance-event.tc"
Date: Wed, 6 Sep 2023 10:37:18 -0400 [thread overview]
Message-ID: <20230906103718.0405ccb4@gandalf.local.home> (raw)
In-Reply-To: <20230906142652.191866-1-naresh.kamboju@linaro.org>
On Wed, 6 Sep 2023 19:56:52 +0530
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> [my two cents]
>
> I do see similar kernel panic while running ftrace testing on today's
> Linux next-20230906 tag. This crash is from qemu-arm64.
>
> Here I am providing steps to reproduced link and scripts by using tuxrun tool.
> - https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2V0OqxEZUXIPNqWhQnnsuFOGYxR/reproducer
>
[..]
> Log details,
> -------------
> # ok 45 ftrace - test tracing error log support
> <47>[ 1373.662292] systemd-journald[90]: Sent WATCHDOG=1 notification.
> # ok 46 Test creation and deletion of trace instances while setting an event
It's definitely a race with the creation and deletion of instances.
I'm going to run it on my laptop VM and see if that reproduces it. My other
VM is on a pretty powerful machine, and perhaps that's keeping it from
hitting the race.
-- Steve
> <1>[ 1382.873224] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000030
> <1>[ 1382.873223] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000030
> <1>[ 1382.873426] Mem abort info:
next prev parent reply other threads:[~2023-09-06 14:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 0:11 [PATCH] selftests/ftrace: Correctly enable event in instance-event.tc Zheng Yejian
2023-06-26 10:11 ` Masami Hiramatsu
2023-06-26 10:12 ` Masami Hiramatsu
2023-07-10 22:37 ` Steven Rostedt
2023-09-05 12:54 ` Zheng Yejian
2023-09-05 16:25 ` Steven Rostedt
2023-09-05 16:49 ` Steven Rostedt
2023-09-05 18:45 ` Steven Rostedt
2023-09-05 20:32 ` Steven Rostedt
2023-09-06 1:26 ` Zheng Yejian
2023-09-05 22:36 ` Steven Rostedt
2023-09-06 1:42 ` Zheng Yejian
2023-09-06 11:27 ` Steven Rostedt
2023-09-06 11:57 ` Zheng Yejian
2023-09-06 12:56 ` Steven Rostedt
2023-09-06 13:02 ` Steven Rostedt
2023-09-06 13:31 ` Zheng Yejian
2023-09-06 13:43 ` Steven Rostedt
2023-09-06 13:45 ` Steven Rostedt
2023-09-06 14:01 ` Zheng Yejian
2023-09-06 14:04 ` Steven Rostedt
2023-09-05 22:43 ` Shuah Khan
2023-09-06 1:45 ` Zheng Yejian
2023-09-06 14:26 ` "[PATCH] selftests/ftrace: Correctly enable event in instance-event.tc" Naresh Kamboju
2023-09-06 14:37 ` Steven Rostedt [this message]
2023-09-06 21:37 ` Steven Rostedt
2023-09-07 1:01 ` Zheng Yejian
2023-09-06 18:50 ` Steven Rostedt
2023-09-06 22:46 ` Steven Rostedt
2023-09-07 1:39 ` Zheng Yejian
2023-09-07 1:44 ` Steven Rostedt
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=20230906103718.0405ccb4@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akaher@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=yeweihua4@huawei.com \
--cc=zhengyejian1@huawei.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;
as well as URLs for NNTP newsgroup(s).