Re: bpftool uses wrong order of tracefs search

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 11, 2025 at 2:03 PM Quentin Monnet <qmo@xxxxxxxxxx> wrote:
>
> 2025-09-11 10:27 UTC-0700 ~ Alexei Starovoitov
> <alexei.starovoitov@xxxxxxxxx>
> > 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?

Older kernels won't have this warn.
Also I don't know what these are:
                "/tracing",
                "/trace",
I think the fix would be to do:
"/sys/kernel/tracing",
"/sys/kernel/debug/tracing",





[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux