ref_tracker_dir_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

ref_tracker_dir_init β€” bestie, this is the one that initializes a ref_tracker dir ✨


🌸 SYNOPSIS 🌸

void ref_tracker_dir_init (struct ref_tracker_dir *dir , unsigned int
quarantine_count , const char *class );

πŸŽ€ ARGUMENTS πŸŽ€

  • dir β€” the ref_tracker_dir that's getting initialized, like it's getting its glam done πŸ’…
  • quarantine_count β€” the max number of entries that can be tracked, no cap on how much it can hold past this πŸ‘€
  • class β€” pointer to a static string describing the object type, so it's giving "permanent label" energy, not "random stack string" energy 🏷️

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so this literally just initializes a ref_tracker_dir 🫢. That's the whole vibe.

But also β€” if debugfs is configured, then a file gets created for it under the top-level ref_tracker debugfs directory too. So you get a little debugfs artifact out of the deal, slay ✨.

⚠️ Heads up bestie, this is the important one: class must point to a static string. Not a stack buffer, not some temporary thing you made two lines ago. Static. Periodt πŸ’€

🌈 SEE ALSO 🌈

  • Kernel file ./include/linux/ref_tracker.h β€” go read it, iykyk πŸ“–

And that's the whole page, bestie πŸ’œ β€” brought to you by ./include/linux, dated October 2026, from the ref_tracker_dir_init(9) chapter of the Kernel API Manual. Go forth and initialize responsibly πŸ§šβ€β™€οΈβ­πŸ”₯

πŸ“¦ where this page comes from