wbc_account_cgroup_owner(9)

✨ NAME ✨

wbc_account_cgroup_owner — bestie, this is the one that accounts writeback so it can update the cgroup ownership of an inode 💅

(it lives in the Kernel API Manual, section 9, if you were wondering 🎀)

---

🌸 SYNOPSIS 🌸

void wbc_account_cgroup_owner (struct writeback_control *wbc , struct
folio *folio , size_t bytes );

---

🦋 ARGUMENTS 🦋

• wbc — the writeback_control of the writeback that's currently in progress, i.e. the vibe check for the writeout happening right now ✨
• folio — the folio that's being written out, the actual main character here 🫶
• bytes — literally how many bytes are being written out, keep count bestie 🔢

---

💖 DESCRIPTION 💖

okay so bytes from folio are about to be written out during the writeback that wbc is controlling. That's the whole situation.

What you do with that: keep the book for foreign inode detection 👑 — like, maintain the accounting, don't skip it, it matters. And for the full picture on that whole thing, go see wbc_detach_inode.

---

⭐ SEE ALSO ⭐

Kernel file ./fs/fs-writeback.c — and honestly the whole friend group shows up here, so let's give them their moment 🎀

• inode_io_list_move_locked(9)
• wb_wait_for_completion(9)
• inode_cgwb_move_to_attached(9)
• locked_inode_to_wb_and_lock_list(9)
• inode_to_wb_and_lock_list(9)
• inode_switch_wbs(9)
• cleanup_offline_cgwb(9)
• wbc_attach_and_unlock_inode(9)
• wbc_attach_fdatawrite_inode(9)
• wbc_detach_inode(9)
• wb_split_bdi_pages(9)
• bdi_split_work_to_wbs(9)
• cgroup_writeback_by_id(9)
• cgroup_writeback_umount(9)
• wb_start_background_writeback(9)
• filemap_dontcache_kick_writeback(9)
• __mark_inode_dirty(9)
• writeback_inodes_sb_nr(9)
• writeback_inodes_sb(9)
• try_to_writeback_inodes_sb(9)
• sync_inodes_sb(9)
• write_inode_now(9)
• sync_inode_metadata(9)

---

💀 reminder bestie: this page is from ./fs, dated October 2026 — so if you're reading this in some other kernel era, double-check before you @ me, fr fr 🌈

laterz, go account those bytes 💜🧚