ref_tracker_dir_init(9)
π 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β theref_tracker_dirthat'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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms