Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: [PATCH 0/2] testing/selftests: Have instance test stress instances more
Date: Thu, 29 Oct 2026 16:28:49 -0400	[thread overview]
Message-ID: <20261029202849.245864353@kernel.org> (raw)

I found that the instance test doesn't actually stress the creation
and deletion of instances while reading them as I thought it did.
This was due to the rmdir failing to remove the instance because it
was busy (by the reads that were happening).

Make the tests do 10 creations and removals while reading the instance
and mkae sure the removal succeeds.

Also add reading of more files that were not tested before.

Steven Rostedt (2):
      tracing/selftests: Fix instance test actually test races
      tracing/selftests: Add reading all instance files to instance test

----
 .../ftrace/test.d/instances/instance-event.tc      | 34 ++++++++++++++++------
 1 file changed, 25 insertions(+), 9 deletions(-)

             reply	other threads:[~2026-10-29 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29 20:28 Steven Rostedt [this message]
2026-10-29 20:28 ` [PATCH 1/2] tracing/selftests: Fix instance test to actually test races Steven Rostedt
2026-10-30  1:01   ` Masami Hiramatsu (Google)
2026-10-30  1:20     ` Steven Rostedt
2026-10-29 20:28 ` [PATCH 2/2] tracing/selftests: Add reading all instance files to instance test Steven Rostedt
2026-10-30  1:24   ` Masami Hiramatsu (Google)

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=20261029202849.245864353@kernel.org \
    --to=rostedt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=skhan@linuxfoundation.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