ext4_double...ite_data_sem(9)

💅 ext4_double...ite_data_sem(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ we're looking at a page whose full title is ext4_double...ite_data_sem(9) (yes the middle got cut off, that's just how it's printed, don't @ me) and the whole vibe is: locking two inodes at once. let's get into it 🫶

🌸 NAME 🌸

ext4_double_down_write_data_sem — write lock two inodes's i_data_sem 🔒🔒 (and yes, "inodes's" is exactly how the original says it, we respect the text 😌)

✨ SYNOPSIS ✨

void ext4_double_down_write_data_sem (struct inode *first , struct inode *second );

🎀 ARGUMENTS 🎀

• first — the inode to be locked, bestie. first one up 💖
• second — the other inode to be locked. the sequel, the second main character 🌟

🦋 DESCRIPTION 🦋

so what does it do? it acquires the write lock of i_data_sem of the two inodes. that's it, that's the whole thing. two inodes, one write lock each, both locked, periodt 💅✨

it's giving "grab both so nobody else can touch them" energy, no cap 🔥

👑 SEE ALSO 👑

• Kernel file ./fs/ext4/move_extent.c ext4_double_up_write_data_sem(9), ext4_move_extents(9) — the related icons, go read them too, iykyk 💜

and that's the page!! 🎀 no notes, ate, left no crumbs ✨ this little beauty lives in ./fs/ext4 and it's stamped October 2026, so like… future-dated slay?? anyway mwah, go lock some inodes responsibly bestie 🌈💖🍓