From: Kalesh Singh <kaleshsingh@google.com>
To: dhowells@redhat.com, rostedt@goodmis.org, mhiramat@kernel.org
Cc: surenb@google.com, jyescas@google.com, kernel-team@android.com,
android-mm@google.com, Kalesh Singh <kaleshsingh@google.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Shuah Khan <shuah@kernel.org>, Ali Zahraee <ahzahraee@gmail.com>,
Eric Sandeen <sandeen@redhat.com>,
Christian Brauner <brauner@kernel.org>,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: [PATCH 0/3] Tracefs gid mount option fixes
Date: Mon, 28 Oct 2024 14:43:56 -0700 [thread overview]
Message-ID: <20241028214550.2099923-1-kaleshsingh@google.com> (raw)
Hi all,
This series is based on v6.12-rc4. It fixes an issue with the tracefs
gid mount option. Adds test case to prevent future breakages and updates
the tracefs readme to document the expected behavior of this option.
Thanks,
Kalesh
Kalesh Singh (3):
tracing: Document tracefs gid mount option
tracing/selftests: Add tracefs mount options test
tracing: Fix tracefs gid mount option
fs/tracefs/inode.c | 12 ++-
kernel/trace/trace.c | 4 +
.../ftrace/test.d/00basic/mount_options.tc | 101 ++++++++++++++++++
.../ftrace/test.d/00basic/test_ownership.tc | 16 +--
.../testing/selftests/ftrace/test.d/functions | 25 +++++
5 files changed, 142 insertions(+), 16 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/00basic/mount_options.tc
base-commit: 42f7652d3eb527d03665b09edac47f85fb600924
--
2.47.0.163.g1226f6d8fa-goog
next reply other threads:[~2024-10-28 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 21:43 Kalesh Singh [this message]
2024-10-28 21:43 ` [PATCH 1/3] tracing: Document tracefs gid mount option Kalesh Singh
2024-10-28 23:12 ` Steven Rostedt
2024-10-28 21:43 ` [PATCH 2/3] tracing/selftests: Add tracefs mount options test Kalesh Singh
2024-10-28 23:14 ` Steven Rostedt
2024-10-28 23:23 ` Kalesh Singh
2024-10-30 17:24 ` Kalesh Singh
2024-10-28 21:43 ` [PATCH 3/3] tracing: Fix tracefs gid mount option Kalesh Singh
2024-10-29 3:00 ` Eric Sandeen
2024-10-29 21:33 ` Kalesh Singh
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=20241028214550.2099923-1-kaleshsingh@google.com \
--to=kaleshsingh@google.com \
--cc=ahzahraee@gmail.com \
--cc=android-mm@google.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=jyescas@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sandeen@redhat.com \
--cc=shuah@kernel.org \
--cc=surenb@google.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