From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.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: Fri, 22 Dec 2023 10:31:48 +0900 [thread overview]
Message-ID: <20231222103148.2f31d91f24134543c0aba382@kernel.org> (raw)
In-Reply-To: <20231221202813.38ef5664@gandalf.local.home>
On Thu, 21 Dec 2023 20:28:13 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 22 Dec 2023 10:21:48 +0900
> Masami Hiramatsu (Google) <mhiramat@kernel.org> wrote:
>
> > The testcase itself is OK but is there any way to identify the system
> > supports eventfs or not? I ran this test on v6.5.13 for checking then
> > it failed. We may need to skip (unsupported) this test for such case.
>
> Hmm, honestly, it should technically work on all past versions.
Ah, sorry. It was my mistake. I need to make /etc/group,passwd files in my test environment.
Let me try it again.
>
> I'll try it out to see what fails for 6.5.13. Perhaps there was another bug
> that the stable releases need fixing for?
>
> -- Steve
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-12-22 1:31 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 [this message]
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
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=20231222103148.2f31d91f24134543c0aba382@kernel.org \
--to=mhiramat@kernel.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=rostedt@goodmis.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).