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>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Anubhav Shelat <ashelat@redhat.com>
Subject: Re: [PATCH v4] tracefs: Add read-only eventfs filesystem at /sys/kernel/events
Date: Mon, 2 Nov 2026 21:53:40 -0500 [thread overview]
Message-ID: <20261102215340.7ce61964@fedora> (raw)
In-Reply-To: <undine-1793672283667563124-a33a39e2a7561653@undined.local>
On Tue, 03 Nov 2026 11:18:03 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
\
> Thanks for the work! As we talked offline, I think we can use this for
> the backup instance (an instance copied from another instance at boot)
> because that backup instance is also read only. See trace_array_is_readonly()
> and TRACE_ARRAY_FL_RDONLY[1].
Will do.
>
> [1] https://lore.kernel.org/all/177502546939.1311542.1826814401724828930.stgit@mhiramat.tok.corp.google.com/
>
> >
> > Assisted-by: CLAUDE:claude-opus-4 Apogee
>
> BTW, this tag seems removed by commit 1e035297ffda ("docs: remove
> Assisted-by references")
As I was one of the first people to advocate for that tag, and I wasn't
invited to the Maintainers Summit to argue against the removal of that
tag, I will not remove any assisted by tags.
It may not be required anymore, but hell, I'll keep them for commits
I'm responsible for. I still find them useful.
-- Steve
prev parent reply other threads:[~2026-11-03 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 20:27 [PATCH v4] tracefs: Add read-only eventfs filesystem at /sys/kernel/events Steven Rostedt
2026-11-02 20:44 ` sashiko-bot
2026-11-02 21:04 ` Steven Rostedt
2026-11-03 2:18 ` Masami Hiramatsu (Google)
2026-11-03 2:53 ` Steven Rostedt [this message]
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=20261102215340.7ce61964@fedora \
--to=rostedt@goodmis.org \
--cc=ashelat@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.