linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Shuah Khan <shuah@kernel.org>,
	Linux selftests <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v2] tracing/selftests: Add ownership modification tests for eventfs
Date: Thu, 21 Dec 2023 21:07:57 -0500	[thread overview]
Message-ID: <20231221210757.112aa4e8@gandalf.local.home> (raw)
In-Reply-To: <20231222105200.e73d58640d8be7da89331deb@kernel.org>

On Fri, 22 Dec 2023 10:52:00 +0900
Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:

> On Fri, 22 Dec 2023 10:48:41 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:

> And I confirmed that this test passed on v6.5.13 with that change.
> 

I just ran it on 6.5.13 and it took *forever*!

But I do have a bit of debug, and before 6.6 creating the instance and
deleting it required creating and deleting thousands of inodes and dentries.

-- Steve

  parent reply	other threads:[~2023-12-22  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22  0:45 [PATCH v2] tracing/selftests: Add ownership modification tests for eventfs Steven Rostedt
2023-12-22  1:21 ` Masami Hiramatsu
2023-12-22  1:28   ` Steven Rostedt
2023-12-22  1:31     ` Masami Hiramatsu
2023-12-22  1:48     ` Masami Hiramatsu
2023-12-22  1:52       ` Masami Hiramatsu
2023-12-22  2:01         ` Steven Rostedt
2023-12-22  2:07         ` Steven Rostedt [this message]
2023-12-22  4:11           ` Masami Hiramatsu

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=20231221210757.112aa4e8@gandalf.local.home \
    --to=rostedt@goodmis.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=shuah@kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).