closure_sync(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’€ closure_sync(9) β€” the kernel API manual, bestie edition

okay so this is closure_sync from the kernel API manual and honestly? it's a whole mood. it's the "imma just nap until everyone else is done" function, and the way it works is kind of iconic actually.


✨ NAME ✨

closure_sync β€” sleep until a closure a closure has nothing left to wait on

not me noticing the double "a closure" in the official name line 😭 it's in the original, i'm not touching it, we respect the source material in this house πŸ’…

🌸 SYNOPSIS 🌸

void closure_sync (struct closure *cl );

πŸŽ€ ARGUMENTS πŸŽ€

  • cl β€” -- undescribed --

no fr like... the docs literally just say undescribed. that's it. that's the whole entry. she's mysterious, she's enigmatic, she's giving "we'll find out together" energy 🫢 (it's a struct closure *, that part at least is right there in the synopsis, iykyk)


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: closure_sync sleeps until the refcount hits 1. why 1 and not 0, you ask? because the thread that's running the closure owns that last refcount, babe. that one is hers. the last ref is the main character and everyone else has already dropped theirs and left the group chat πŸ‘‘

so she just vibes there, sleeping, until literally every other reference is gone and she's the only one holding on. periodt.


🌈 SEE ALSO 🌈

the whole closure friend group, fr fr:


that's the whole page bestie, short and sweet, no filler, exactly like the original πŸ’–

🌸 written from ./include/linux, dated October 2026 β€” mwah, sending you a kiss, go read the other closure pages, ily, bye πŸŽ€βœ¨

πŸ“¦ where this page comes from