From: Quentin Monnet <qmo@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
bpf <bpf@vger.kernel.org>, Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: bpftool uses wrong order of tracefs search
Date: Thu, 11 Sep 2025 22:03:54 +0100 [thread overview]
Message-ID: <35d7e2b8-c090-46fc-8f45-b976ffbd5dce@kernel.org> (raw)
In-Reply-To: <CAADnVQLcMi5YQhZKsU4z3S2uVUAGu_62C33G2Zx_ruG3uXa-Ug@mail.gmail.com>
2025-09-11 10:27 UTC-0700 ~ Alexei Starovoitov
<alexei.starovoitov@gmail.com>
> Hi Quentin,
>
> since last merge window bpftool triggers a warn:
> $ bpftool prog tracelog
> [ 72.942082] NOTICE: Automounting of tracing to debugfs is
> deprecated and will be removed in 2030
>
>
> I suspect it happens because get_tracefs_pipe()
> accesses debug/tracing first which causes automnount
> and triggers this warning.
>
> Pls take a look.
Hi Alexei, sure, I'll look into it.
I haven't tested yet, but the check on /sys/kernel/debug/tracing is
likely to be the cause indeed. If that's the case, would that be OK to
move it to the end of the "known_mnts" list in the function? Or do you
prefer to avoid the warning completely, even at the cost of missing the
tracefs on older systems?
Quentin
next prev parent reply other threads:[~2025-09-11 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 17:27 bpftool uses wrong order of tracefs search Alexei Starovoitov
2025-09-11 21:03 ` Quentin Monnet [this message]
2025-09-11 21:32 ` Alexei Starovoitov
2025-09-11 21:39 ` Steven Rostedt
2025-09-11 21:42 ` Alexei Starovoitov
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=35d7e2b8-c090-46fc-8f45-b976ffbd5dce@kernel.org \
--to=qmo@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=martin.lau@kernel.org \
--cc=rostedt@goodmis.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.