dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jeff Layton <jlayton@kernel.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Kuniyuki Iwashima" <kuniyu@amazon.com>,
	"Qasim Ijaz" <qasdev00@gmail.com>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Andrew Lunn" <andrew@lunn.ch>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH v11 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir
Date: Wed, 28 May 2025 14:47:30 -0700	[thread overview]
Message-ID: <20250528144730.57741830@kernel.org> (raw)
In-Reply-To: <20250528-reftrack-dbgfs-v11-0-94ae0b165841@kernel.org>

On Wed, 28 May 2025 10:34:32 -0400 Jeff Layton wrote:
> Changes in v10:
> - drop the i915 symlink patch
> - Link to v9: https://lore.kernel.org/r/20250509-reftrack-dbgfs-v9-0-8ab888a4524d@kernel.org

Hm, I reported the refracker warnings at boot on v9 :
   ref_tracker: ref_tracker: unable to create debugfs file for net_refcnt@ffffffffb73a98f0: -ENOENT
   ref_tracker: ref_tracker: unable to create debugfs file for net_notrefcnt@ffffffffb73a9978: -ENOENT

Did you decide against fixing those? 
Or did they creep back in?

      parent reply	other threads:[~2025-05-28 21:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 14:34 [PATCH v11 00/10] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir Jeff Layton
2025-05-28 14:34 ` [PATCH v11 01/10] i915: only initialize struct ref_tracker_dir once Jeff Layton
2025-05-28 14:34 ` [PATCH v11 02/10] ref_tracker: don't use %pK in pr_ostream() output Jeff Layton
2025-05-28 14:34 ` [PATCH v11 03/10] ref_tracker: add a top level debugfs directory for ref_tracker Jeff Layton
2025-05-28 14:34 ` [PATCH v11 04/10] ref_tracker: have callers pass output function to pr_ostream() Jeff Layton
2025-05-28 14:34 ` [PATCH v11 05/10] ref_tracker: add a static classname string to each ref_tracker_dir Jeff Layton
2025-05-28 14:34 ` [PATCH v11 06/10] ref_tracker: allow pr_ostream() to print directly to a seq_file Jeff Layton
2025-05-28 14:34 ` [PATCH v11 07/10] ref_tracker: automatically register a file in debugfs for a ref_tracker_dir Jeff Layton
2025-05-28 14:34 ` [PATCH v11 08/10] ref_tracker: add a way to create a symlink to the ref_tracker_dir debugfs file Jeff Layton
2025-05-28 14:34 ` [PATCH v11 09/10] net: add symlinks to ref_tracker_dir for netns Jeff Layton
2025-05-28 14:34 ` [PATCH v11 10/10] ref_tracker: eliminate the ref_tracker_dir name field Jeff Layton
2025-05-28 21:47 ` Jakub Kicinski [this message]

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=20250528144730.57741830@kernel.org \
    --to=kuba@kernel.org \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=jlayton@kernel.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=kuniyu@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=nathan@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qasdev00@gmail.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.weissschuh@linutronix.de \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).