nilfs_ioctl_clean_segments(9)

📦 version 7.3.1, in nixpkgs unstable

💖 nilfs_ioctl_clean_segments 💖

okay bestie so we're in the kernel API manual rn, specifically the nilfs_ioctl_clean_segments(9) page — yes the whole thing is named after the function, iconic behavior honestly 🎀

✨ SYNOPSIS ✨

like, the whole signature, verbatim, no cap:

int nilfs_ioctl_clean_segments (struct inode *inode , struct file *filp
, unsigned int cmd , void __user *argp );

she takes four things and she's gonna tell you about all four, let's go 🌸

🦋 ARGUMENTS 🦋

  • inode — the inode object, our main character for this call 👑
  • filp — the file object, tagging along 🫶
  • cmd — the ioctl's request code, aka which thing we're asking for
  • argp — a pointer on the argument from userspace, i.e. the userland side's lil package of info dropped off at kernel's door 💌

💅 DESCRIPTION 💅

so nilfs_ioctl_clean_segments literally does a garbage collection operation, and it does it in the environment of the requested parameters that came in from userspace. the NILFS_IOCTL_CLEAN_SEGMENTS ioctl is the one being used here — and it's used by the nilfs_cleanerd daemon. yep, the daemon is the one sliding into this function's DMs 😭💀

⭐ RETURN ⭐

  • 0 — on success, slay ✨
  • a negative error code — on failure, not slay 🙈

🌈 SEE ALSO 🌈

the reading list, no skipping, periodt:

and that's the tea, bestie 🍓 this page lives at ./fs/nilfs2, dated October 2026, and it's nilfs_ioctl_clean_segments(9) — go forth and collect your garbage, mwah 💜

📦 where this page comes from