From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
"linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Namhyung Kim <namhyung@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>
Subject: Re: [RFC][PATCH] tracing: Deprecate auto-mounting tracefs in debugfs
Date: Wed, 18 Jun 2025 09:21:02 +0200 [thread overview]
Message-ID: <20250618072102.1fnuVt8d@linutronix.de> (raw)
In-Reply-To: <20250617180023.GC1613376@noisy.programming.kicks-ass.net>
On 2025-06-17 20:00:23 [+0200], Peter Zijlstra wrote:
> If I have to edit the mount table, I'll just keep it at /debug/tracing/.
> Tracing is very much debug stuff anyway. While I knew there was tracefs,
> I never knew there was another mount point.
>
> Just annoying I now have to add two entries to every new machine.. Oh
> well.
I don't know what you run but since Debian 11/ Bullseye (v5.10) this happens
more or less on its own. systemd has the proper mount units:
| # mount | grep trace
| tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
| # ls -lh /sys/kernel/debug/tracing/ > /dev/null
| # mount | grep trace
| tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
| tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
This of course doesn't work if you manually mount it to /debug. While a
symlink would work, you still have to touch the boxes.
Sebastian
next prev parent reply other threads:[~2025-06-18 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 17:36 [RFC][PATCH] tracing: Deprecate auto-mounting tracefs in debugfs Steven Rostedt
2025-06-17 17:41 ` Peter Zijlstra
2025-06-17 17:54 ` Steven Rostedt
2025-06-17 18:00 ` Peter Zijlstra
2025-06-17 18:48 ` Ian Rogers
2025-06-17 19:14 ` Steven Rostedt
2025-06-18 7:21 ` Sebastian Andrzej Siewior [this message]
2025-06-18 9:27 ` Peter Zijlstra
2025-06-17 19:29 ` Steven Rostedt
2025-06-18 9:18 ` Christian Brauner
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=20250618072102.1fnuVt8d@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=irogers@google.com \
--cc=jack@suse.cz \
--cc=jolsa@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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