nilfs_ioctl_do_get_vinfo(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ nilfs_ioctl_do_get_vinfo β€” the Kernel API Manual, bestie edition ✨

Okay so this page is nilfs_ioctl_do_get_vinfo(9) from the Kernel API Manual, and it's literally the callback that fetches your virtual block info. Tiny function, big group-chat energy. Let's get into it πŸ’…


✨ NAME ✨

nilfs_ioctl_do_get_vinfo β€” the callback method that gets virtual blocks info πŸ¦‹


🌸 SYNOPSIS 🌸

ssize_t nilfs_ioctl_do_get_vinfo (struct the_nilfs *nilfs , __u64 *posp
, int flags , void *buf , size_t size , size_t nmembs );

That's the whole signature, no cap. Six arguments, one return type, all of it exact πŸŽ€


πŸ’– ARGUMENTS πŸ’–

  • nilfs β€” the nilfs object, obvs. This is your main character right here πŸ‘‘
  • posp β€” not used πŸ™ˆ literally just vibing there, ignored
  • flags β€” not used too 😭 also ignored, don't even worry about it
  • buf β€” the buffer where the array of nilfs_vinfo structures gets stored πŸ“
  • size β€” size in bytes of one vinfo item in the array, so like, the per-item footprint ngl
  • nmembs β€” the count of vinfos in the array. how many we're working with, fr fr

πŸ”₯ DESCRIPTION πŸ”₯

So the nilfs_ioctl_do_get_vinfo function returns information on virtual block addresses ✨ That's the whole gig and it ate.

The NILFS_IOCTL_GET_VINFO ioctl is the one that gets used by the nilfs_cleanerd daemon β€” so if you were wondering who's calling this, it's them, iykyk 🧚


🌈 RETURN 🌈

On success? It hands you back the count of nilfs_vinfo structures in the output buffer πŸ’– On failure? A negative error code 😭 that's the vibe check failing, respectfully.


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./fs/nilfs2/ioctl.c, plus the whole friend group:


Okay that's the whole page bestie, go read the source if you want more lore πŸ“š

Sign-off time 🫢 this little masterpiece lives in ./fs/nilfs2, it's dated October 2026, and it's filed under nilfs_ioctl_do_get_vinfo(9). Slay, periodt πŸ’…βœ¨

πŸ“¦ where this page comes from