netfs_singl..._inode_dirty(9)

✨ netfs_single_mark_inode_dirty(9) ✨

okay so bestie, welcome to the Kernel API Manual 💅 this one's a lil function from the netfs world, and honestly? she's short, she's sweet, she does exactly one thing and she does it slayfully. let's get into it 🎀

---

🌸 NAME 🌸

netfs_single_mark_inode_dirty — marks a single, monolithic object inode as dirty 🔥

no cap, that's the whole vibe. one inode, one monolithic object, one little dirty flag. iconic.

---

🦋 SYNOPSIS 🦋

void netfs_single_mark_inode_dirty (struct inode *inode );

that's it. that's the signature. returns void, takes one pointer, zero drama 🙈

---

🍓 ARGUMENTS 🍓

• inode — the inode you're marking, bestie. the one. the main character 👑

---

💖 DESCRIPTION 💖

so here's the tea ☕ — you call this bad girl on an inode that contains a single, monolithic object, and she marks it as dirty so that its writepages op will get called. that's the whole point. that's her job. she ate and left no crumbs 💅

and listen, there's this flag called SINGLE_NO_UPLOAD — if it's set, it means the object is only gonna be written to the cache and not uploaded anywhere. the manpage literally gives you the example: AFS directory contents 📁✨ so like, cache-only behaviour, no shipping it off to the server, iykyk.

fr fr, don't forget: the flag has to be set for that cache-only behaviour to kick in. if it's not set, that's a whole different story and we're not telling it here 🫶

---

🌈 SEE ALSO 🌈

• Kernel file ./fs/netfs/read_single.c 📄
• netfs_read_single(9) 👀 — go read the sibling page, she's also great

---

and that's the whole page, bestie!! 🧚💜 huge shoutout to the source tree ./fs/netfs and the date stamp October 2026 — that's where this lil beauty lives, mwah 💋⭐