[PATCH v4 0/7] ref_tracker: add ability to register a debugfs file for a ref_tracker_dir
From: Jeff Layton
Date: Fri Apr 18 2025 - 10:24:46 EST
This version should be pretty close to merge-ready. The only real
difference is the use of NAME_MAX as the field width for on-stack
sprintf buffers.
I left the Reviewed-bys intact. Let me know if that's an issue and
we can drop them.
Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx>
---
Changes in v4:
- Drop patch to widen ref_tracker_dir_.name, use NAME_MAX+1 (256) instead since this only affects dentry name
- Link to v3: https://lore.kernel.org/r/20250417-reftrack-dbgfs-v3-0-c3159428c8fb@xxxxxxxxxx
Changes in v3:
- don't overwrite dir->name in ref_tracker_dir_debugfs
- define REF_TRACKER_NAMESZ and use it when setting name
- Link to v2: https://lore.kernel.org/r/20250415-reftrack-dbgfs-v2-0-b18c4abd122f@xxxxxxxxxx
Changes in v2:
- Add patch to do %pK -> %p conversion in ref_tracker.c
- Pass in output function to pr_ostream() instead of if statement
- Widen ref_tracker_dir.name to 64 bytes to accomodate unique names
- Eliminate error handling with debugfs manipulation
- Incorporate pointer value into netdev name
- Link to v1: https://lore.kernel.org/r/20250414-reftrack-dbgfs-v1-0-f03585832203@xxxxxxxxxx
---
Jeff Layton (7):
ref_tracker: don't use %pK in pr_ostream() output
ref_tracker: add a top level debugfs directory for ref_tracker
ref_tracker: have callers pass output function to pr_ostream()
ref_tracker: allow pr_ostream() to print directly to a seq_file
ref_tracker: add ability to register a file in debugfs for a ref_tracker_dir
net: add ref_tracker_dir_debugfs() calls for netns refcount tracking
net: register debugfs file for net_device refcnt tracker
include/linux/ref_tracker.h | 13 ++++
lib/ref_tracker.c | 151 +++++++++++++++++++++++++++++++++++++++-----
net/core/dev.c | 6 +-
net/core/net_namespace.c | 34 +++++++++-
4 files changed, 187 insertions(+), 17 deletions(-)
---
base-commit: 695caca9345a160ecd9645abab8e70cfe849e9ff
change-id: 20250413-reftrack-dbgfs-3767b303e2fa
Best regards,
--
Jeff Layton <jlayton@xxxxxxxxxx>