mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zheng Yejian <zhengyejian1@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: <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: Thu, 7 Sep 2023 09:01:30 +0800	[thread overview]
Message-ID: <eb050960-b2bb-4dbe-7879-a0dd3935556e@huawei.com> (raw)
In-Reply-To: <20230906173706.7aeb8716@gandalf.local.home>

On 2023/9/7 05:37, Steven Rostedt wrote:
> On Wed, 6 Sep 2023 10:37:18 -0400
> Steven Rostedt <rostedt@goodmis.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
> 

In test.d/instances/instance-event.tc, concurrently create/delete/access
intances just about 1 second and then killed them, it may cause missing
the race.

No longer sleep and kill, following testcase can also reproduce:
```
#!/bin/bash

cd /sys/kernel/tracing/instances

instance_slam() {
   while :; do
           mkdir foo 2> /dev/null
           rmdir foo 2> /dev/null
   done
}

instance_set() {
         while :; do
                 echo 1 > foo/events/sched/sched_switch/enable
         done 2> /dev/null
}

instance_slam &
p1=$!
echo $p1

instance_set &
p2=$!
echo $p2
```

--

Thanks,
Zheng Yejian

> 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
> 


  reply	other threads:[~2023-09-07  1:01 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
2023-09-06 21:37                 ` Steven Rostedt
2023-09-07  1:01                   ` Zheng Yejian [this message]
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=eb050960-b2bb-4dbe-7879-a0dd3935556e@huawei.com \
    --to=zhengyejian1@huawei.com \
    --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=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=yeweihua4@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

all inboxes | Powered by JetHome®