[PATCH v9 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir
Jeff Layton
jlayton at kernel.org
Sat May 10 11:17:35 UTC 2025
On Fri, 2025-05-09 at 16:00 -0700, Jakub Kicinski wrote:
> On Fri, 09 May 2025 11:53:36 -0400 Jeff Layton wrote:
> > This one just fixes a typo in the ref_tracker_dir_init() kerneldoc
> > header. I'm only resending so the CI will pick it up.
>
> We got a bunch of:
>
> [ 0.457561][ T0] ref_tracker: ref_tracker: unable to create debugfs file for net_refcnt at ffffffff92da4870: -ENOENT
> [ 0.457561][ T0] ref_tracker: ref_tracker: unable to create debugfs file for net_notrefcnt at ffffffff92da48f8: -ENOENT
>
> [ 0.973191][ T1] ref_tracker: ref_tracker: unable to create debugfs file for netdev at ffff888004d0c5a8: -ENOENT
>
> [ 1.150784][ T1] ref_tracker: ref_tracker: unable to create debugfs file for netdev at ffff8880053fc5a8: -ENOENT
>
> [ 1.660680][ T1] ref_tracker: ref_tracker: unable to create debugfs file for netdev at ffff8880085f95a8: -ENOENT
>
> in the CI at boot. Presumably init_net and loopback.
>
> https://netdev-3.bots.linux.dev/vmksft-net-drv-dbg/results/113741/vm-start-thr0-0/stdout
Makes sense. I had an earlier version that only attempted to create the
debugfs file if the directory was already created, but Andrew had
complained about the error checking I was doing on debugfs. That would
silence these warnings. I'll see about bringing that back.
--
Jeff Layton <jlayton at kernel.org>
More information about the Intel-gfx
mailing list