From: Daniel Borkmann <daniel@iogearbox.net>
To: Quentin Monnet <qmo@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpftool: Search for tracefs at /sys/kernel/tracing first
Date: Mon, 15 Sep 2025 13:33:56 +0200 [thread overview]
Message-ID: <055e1c7a-410f-4843-bec4-e545f032b145@iogearbox.net> (raw)
In-Reply-To: <20250912104343.58555-1-qmo@kernel.org>
On 9/12/25 12:43 PM, Quentin Monnet wrote:
[...]
> diff --git a/tools/bpf/bpftool/tracelog.c b/tools/bpf/bpftool/tracelog.c
> index 31d806e3bdaa..49828a4f60c2 100644
> --- a/tools/bpf/bpftool/tracelog.c
> +++ b/tools/bpf/bpftool/tracelog.c
> @@ -57,10 +57,8 @@ find_tracefs_mnt_single(unsigned long magic, char *mnt, const char *mntpt)
> static bool get_tracefs_pipe(char *mnt)
> {
> static const char * const known_mnts[] = {
> - "/sys/kernel/debug/tracing",
> "/sys/kernel/tracing",
> - "/tracing",
> - "/trace",
> + "/sys/kernel/debug/tracing",
> };
> const char *pipe_name = "/trace_pipe";
> const char *fstype = "tracefs";
> @@ -96,11 +94,11 @@ static bool get_tracefs_pipe(char *mnt)
>
> p_info("could not find tracefs, attempting to mount it now");
> /* Most of the time, tracefs is automatically mounted by debugfs at
> - * /sys/kernel/debug/tracing when we try to access it. If we could not
> + * /sys/kernel/tracing when we try to access it. If we could not
> * find it, it is likely that debugfs is not mounted. Let's give one
nit: Should this comment be tweaked further, or maybe even removed completely
given the now stale references to debugfs there?
> * attempt at mounting just tracefs at /sys/kernel/tracing.
> */
> - strcpy(mnt, known_mnts[1]);
> + strcpy(mnt, known_mnts[0]);
> if (mount_tracefs(mnt))
> return false;
>
next prev parent reply other threads:[~2025-09-15 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 10:43 [PATCH bpf-next] bpftool: Search for tracefs at /sys/kernel/tracing first Quentin Monnet
2025-09-15 11:33 ` Daniel Borkmann [this message]
2025-09-15 11:47 ` Quentin Monnet
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=055e1c7a-410f-4843-bec4-e545f032b145@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=qmo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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