ovl_statfs(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ ovl_statfs(9) β€” a Kernel API Manual moment πŸ¦‹

okay so bestie, you're in the Kernel API Manual and today's main character is ovl_statfs(9). pull up a chair, hydrate, and let's get into it πŸ’…


✨ NAME ✨

ovl_statfs β€”

and that's... literally it 😭 the description field is empty, our girl showed up to the function with no bio. iconic behaviour honestly, she lets the code speak for itself 🫢


🌸 SYNOPSIS 🌸

int ovl_statfs (struct dentry *dentry , struct kstatfs *buf );

πŸŽ€ ARGUMENTS πŸŽ€

  • dentry β€” the dentry you're querying πŸ‘€ this is the thing you're asking about, so like, be normal about it.
  • buf β€” the struct kstatfs you're gonna fill in with the stats ✨ she's empty when she arrives, and full of numbers when she leaves. a glow-up fr.

πŸ’– DESCRIPTION πŸ’–

so the whole vibe here is: get the filesystem statistics πŸ“Š that's the job, that's the assignment.

but here's the tea πŸ”₯ β€” because writes always target the upper layer filesystem, you pass the statfs on to the upper filesystem. like, hand it off. give it to the upper layer. (if it exists, obviously πŸ™ˆ β€” no upper layer, no handoff, simple as.)

ngl the way this function just delegates to the upper layer is giving "I trust you with this" energy 🀝


πŸ”₯ SEE ALSO πŸ”₯

  • Kernel file ./fs/overlayfs/super.c β€” go read her, she's got the lore 🧚

fr fr: every detail up there matters, dentry and buf are real arguments and struct kstatfs is a real struct β€” don't get cute and rename things, that's not the vibe πŸ’€

and that's the whole page, bestie ✨ this lil' slice of the Kernel API Manual lives at ./fs/overlayfs, and it's stamped October 2026 πŸŽ€ so if you're reading this in some other timeline... no you're not πŸ¦‹ mwah, slay, bye πŸ’œ

πŸ“¦ where this page comes from