nilfs_dat_mark_dirty(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nilfs_dat_mark_dirty ✨

okay so bestie, welcome to the kernel API manual for nilfs_dat_mark_dirty πŸ’– yes that's the whole name, she's long but she's iconic, and today we're learning what she does. grab a snack πŸ“


🌸 NAME 🌸

nilfs_dat_mark_dirty β€” marks the DAT block buffer that holds the specified virtual block address entry as dirty. that's it, that's the job, and honestly? she does it flawlessly πŸŽ€


✨ SYNOPSIS ✨

int nilfs_dat_mark_dirty (struct inode *dat , __u64 vblocknr );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dat β€” the DAT file inode πŸ‘‘ like, the inode, the whole personality
  • vblocknr β€” the virtual block number πŸ’«

πŸ”₯ RETURN πŸ”₯

0 on success πŸŽ‰ (slay), or one of these negative error codes if things go sideways 😭:

  • -EINVAL β€” invalid DAT entry (that's the internal code, iykyk) πŸ™ˆ
  • -EIO β€” I/O error, and yes that includes metadata corruption, so like… be aware πŸ’€
  • -ENOMEM β€” not enough memory available, the classic πŸ˜”
ngl if you see -EIO and it's metadata corruption, that's not a vibe. handle it. 🫢

🌈 SEE ALSO 🌈


and that's the whole page, bestie! πŸ’… this one's from ./fs/nilfs2, dated October 2026, and it goes by nilfs_dat_mark_dirty(9) β€” periodt. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from