sync_inodes_sb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sync_inodes_sb β€” kernel API manual, but make it make sense πŸŽ€

okay so bestie, welcome to the <purple>sync_inodes_sb(9)</purple> page β€” it's a kernel API manual moment, and honestly? It's a short one, so we're gonna get through it together and you're gonna get it. 🫢


✨ NAME ✨

sync_inodes_sb β€” sync sb inode pages, no cap πŸ’«


🌸 SYNOPSIS 🌸

void sync_inodes_sb (struct super_block *sb );

that's it. that's the whole thing. one function, one argument, zero drama. it returns void bestie, so like... don't go looking for a return value, it's not coming. 😌


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sb β€” the superblock πŸ’– β€” literally the superblock, that's the whole description, she's doing her job and saying exactly what she needs to say.

πŸ‘‘ DESCRIPTION πŸ‘‘

okay so here's the actual tea β˜• β€” this function writes and waits on any dirty inode belonging to this super_block.

read that again, because both halves matter, fr fr:

  1. it writes the dirty inodes β€” like, flushes them out ✍️
  2. and it waits on them β€” it does not just fire and forget, it stays there until they're done 🧚

and it only touches inodes that belong to this super_block. not the neighbours, not the other filesystems, just hers. main character energy, honestly. πŸ‘‘

🫢 little reminder that "dirty" here is a whole technical thing (inodes with unsaved changes pending) β€” not a judgement on the inode's hygiene. she's doing great.

πŸ’œ SEE ALSO πŸ’œ

so you wanna go deeper? periodt, let's go β€” here's the whole squad, all in the kernel file ./fs/fs-writeback.c:

iykyk β€” that's a lot of writeback friends, and they all live together in ./fs/fs-writeback.c. go say hi. 🌈


and that's the page!! ✨ sign-off time: this lil manual page comes from <pink>./fs</pink>, dated <pink>October 2026</pink>, and it's filed under sync_inodes_sb(9) in the Kernel API Manual. slay, go sync some inodes, and remember β€” write and wait. πŸ’…πŸŽ€

πŸ“¦ where this page comes from