continue_at(9)

💅 continue_at(9) 💅

okay so welcome to the Kernel API Manual, bestie — today’s main character is continue_at. the NAME section says it all: jump to another function with barrier. that’s the vibe. ✨

🌸 SYNOPSIS 🌸

continue_at (_cl , _fn , _wq );

🎀 ARGUMENTS 🎀

• _cl — the manpage literally gives us -- undescribed -- 😭 no extra lore, bestie.
• _fn — also -- undescribed -- 🙈
• _wq — yep, -- undescribed -- again 💀

🦋 DESCRIPTION 🦋

okay so here’s the plot, no cap: after cl is no longer waiting on anything (i.e. all outstanding refs have been dropped with closure_put), it will resume execution at fn running out of wq. and if wq is NULL, fn will be called by closure_put directly. periodt. 💅

the reason is that after calling continue_at you no longer have a ref on cl, and whatever cl owns may be freed out from under you — a running closure fn has a ref on its own closure which continue_at drops. so like, that’s the ref math, bestie. 🫶

⚠️ note: you are expected to immediately return after using this macro. no cap. 😤

🌈 SEE ALSO 🌈

related lore lives in Kernel file ./include/linux/closure.h — go read these, iykyk:

• closure_sync(9)
• closure_get(9)
• closure_get_not_zero(9)
• closure_init(9)
• closure_wake_up(9)
• closure_return(9)
• continue_at_nobarrier(9)
• closure_return_with_destructor(9)
• closure_call(9)

xoxo, your kernel bestie 💖 — sourced from ./include/linux, dated October 2026. slay. 💅