nilfs_dirty_inode(9)

✨ nilfs_dirty_inode 💅

okay so real talk, this is a page from the Kernel API Manual — section 9, kernel developer land 🧚 — and it's all about nilfs_dirty_inode(9). yes bestie, the whole page is literally named after the function. iconic behavior honestly 👑

---

🌸 NAME 🌸

nilfs_dirty_inode — the girl whose entire job is reflecting changes on a given inode over into an inode block ✨

---

🎀 SYNOPSIS 🎀

void nilfs_dirty_inode (struct inode *inode , int flags );

that's it. that's the whole signature. no return value, she's a void, she doesn't need to report back 💅

---

🦋 ARGUMENTS 🦋

• inode — the inode of the file that's getting registered. this is the main character of the operation 🌟
• flags — the flags that determine the dirty state of the inode. like, what kind of dirty are we talking about here 🙈

---

🔥 DESCRIPTION 🔥

so what does she actually do? okay so nilfs_dirty_inode loads up an inode block that contains the specified inode, and then copies data from a nilfs_inode into the corresponding inode entry inside that inode block. that's the whole glow-up: the in-memory vibes get written into the on-disk-looking entry, no cap 💖

here's the important caveat though, do not skip this: this operation is excluded from the segment construction. like, she's not part of that process, periodt. keep that straight or you will have a bad time 😭

the good news is she's flexible — this function can be called both as a single standalone operation and as a part of indivisible file operations. so whether she's solo or in a group chat, she shows up and does her thing 🫶

---

⭐ SEE ALSO ⭐

go read these next, bestie, they're all in the kernel file ./fs/nilfs2/inode.c and they're all absolutely part of the same friend group:

• struct nilfs_iget_args(9)
• nilfs_get_block(9)
• nilfs_read_folio(9)
• nilfs_attach_btree_node_cache(9)
• nilfs_detach_btree_node_cache(9)
• nilfs_iget_for_shadow(9)
• nilfs_write_inode_common(9)

---

okay that's the whole page, you ate that 💜 this lil slice of kernel lore comes from ./fs/nilfs2 and it's dated October 2026 — so yeah, she's from the future, we love a time traveler 🌈⭐ mwah, go read nilfs_get_block(9) next, iykyk 🎀