continue_at_nobarrier(9)

💫 continue_at_nobarrier(9) — the kernel API manual, bestie edition 💫

okay so we're in the <hotpink>kernel API manual</hotpink> and today's main character is continue_at_nobarrier(9). yes that's the whole manual name, we're being formal today 🎀

---

✨ NAME ✨

continue_at_nobarrier — jump to another function without a barrier 🦋

no cap, that's literally the entire job description.

---

🌸 SYNOPSIS 🌸

continue_at_nobarrier (_cl , _fn , _wq );

look at those three lil arguments just vibing there. 💅

---

🎀 ARGUMENTS 🎀

• _cl — honestly? undescribed. the docs left this one on read 😭
• _fn — also undescribed. iconic mystery behaviour, ngl.
• _wq — undescribed too. all three of them are giving "we'll figure it out in the source code" energy 💀

yeah bestie, all three arguments literally say -- undescribed -- in the original. i'm not making stuff up, i'm just delivering the truth with better lighting. 🫶

---

🌈 DESCRIPTION 🌈

so here's the vibe: this function causes fn to be executed out of cl, in wq context — or called directly if wq is NULL. 🧚

and this next bit? read it twice, bestie, it's important. 💜

the ref that the caller of continue_at_nobarrier had on cl is now owned by fn. which means it is not safe to touch anything protected by cl after a continue_at_nobarrier. like, at all. do not pass go, do not poke the closure. it's not yours anymore, the ref has left the building 🫡✨

⚠️ fr fr: after continue_at_nobarrier, everything guarded by cl is off-limits to you. the ownership handed off, and poking it anyway is exactly the kind of chaos that ruins everyone's day. 😭

---

⭐ SEE ALSO ⭐

• Kernel file ./include/linux/closure.h — that's the home of all this closure magic 🦋
• closure_sync(9)
• closure_get(9)
• closure_get_not_zero(9)
• closure_init(9)
• closure_wake_up(9)
• continue_at(9) — the barrier-having cousin, iykyk 👀
• closure_return(9)
• closure_return_with_destructor(9)
• closure_call(9)

go read them all, they're the friend group and this page is just one member of it 🌸💖

---

and that's the whole page, bestie!! sourced straight from ./include/linux and dated October 2026 — the kernel API manual really said "it's giving future" and honestly? slay. 👑✨ 💅