inode_cgwb_move_to_attached(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– inode_cgwb_move_to_attached(9) πŸ’–

okay so bestie, we're in the kernel API manual today, and this one is literally called inode_cgwb_move_to_attached β€” say that five times fast, i dare you 🫢. it's a little writeback helper, it's giving backstage-crew energy, and honestly? iconic.


✨ NAME ✨

inode_cgwb_move_to_attached β€” put the inode onto the wb->b_attached list. that's the whole job. no cap. πŸ’…


🌸 SYNOPSIS 🌸

void inode_cgwb_move_to_attached (struct inode *inode , struct
       bdi_writeback *wb );

literally just two args and zero return value. she does her thing and she leaves. main character behaviour, honestly. ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • inode β€” the inode of interest. ⚠️ and you must already be holding i_lock when you call this, that's not optional, that's the vibe check.
  • wb β€” the target bdi_writeback. the destination. the place she's moving to. πŸŽ€

πŸ’œ DESCRIPTION πŸ’œ

so what actually happens? okay so: this function removes the inode from wb's io lists, and if necessarily, puts it onto the b_attached list. πŸ’«

and here's the lil detail that matters β€” only inodes attached to cgwb's are kept on this list. that's the rule. that's the whole membership criteria. iykyk 🧚


πŸ‘‘ SEE ALSO πŸ‘‘

bestie, buckle up, the friend group is huge β€” this is the friend group chat of kernel file ./fs/fs-writeback.c:

like… that's a full roster. go say hi. they're all in there. 🌈


and that's the page, bestie!! πŸŽ€ this lil beauty lives in the ./fs directory and it's dated October 2026, and the whole thing is filed under inode_cgwb_move_to_attached(9) β€” so if you need to find her again, that's the name. mwah. πŸ’–βœ¨πŸ”₯

πŸ“¦ where this page comes from