[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230906173706.7aeb8716@gandalf.local.home>
Date: Wed, 6 Sep 2023 17:37:06 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: zhengyejian1@...wei.com, akaher@...are.com,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, mhiramat@...nel.org,
shuah@...nel.org, skhan@...uxfoundation.org, yeweihua4@...wei.com
Subject: Re: "[PATCH] selftests/ftrace: Correctly enable event in
instance-event.tc"
On Wed, 6 Sep 2023 10:37:18 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> > 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.
Putting in a while loop of:
# while :; do ./ftracetest test.d/instances/instance-event.tc ; done
eventually triggered the bug. Looks like this is really an existing bug not
related to the eventfs, but the eventfs code actually opened up the window
of this race.
Hopefully I'll have a fix shortly.
-- Steve
Powered by blists - more mailing lists