inode_io_list_move_locked(9)

okay bestie, welcome to the inode_io_list_move_locked(9) page from the Kernel API Manual 💅✨ this one is short but it's literally doing important writeback list choreography, so let's get into it.

🌸 NAME 🌸

inode_io_list_move_locked — move an inode onto a bdi_writeback IO list. periodt 💖

🎀 SYNOPSIS 🎀

bool inode_io_list_move_locked (struct inode *inode , struct
       bdi_writeback *wb , struct list_head *head );

🦋 ARGUMENTS 🦋

• inode — the inode to be moved 🫶
• wb — target bdi_writeback
• head — literally one of wb->b_{dirty|io|more_io|dirty_time} 💅

🔥 DESCRIPTION 🔥

okay so the move is: take inode->i_io_list, move it to the list of wb, and set WB_has_dirty_io. 🎀

the return vibe is true if inode is the first occupant of the !dirty_time IO lists; otherwise, it's false. that's the whole tea, no cap 🫖✨

💜 SEE ALSO 💜

go touch grass in these, bestie:

• Kernel file ./fs/fs-writeback.c
• 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)
• wbc_account_cgroup_owner(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)

🎀 cute little sign-off: this iconic page comes from ./fs, dated October 2026, and it's literally the inode_io_list_move_locked(9) manual page. that's the footer, bestie — slay and read the source 💖✨