closure_call(9)

💫 closure_call(9) — Kernel API Manual, section 9, bestie 💫

okay so this is closure_call(9) from the Kernel API Manual and honestly? it's giving "spawn a whole new closure and let it cook" ✨

---

🌸 NAME 🌸

closure_call — execute @fn out of a new, uninitialized closure 🫶

---

✨ SYNOPSIS ✨

void closure_call (struct closure *cl , closure_fn fn , struct
workqueue_struct *wq , struct closure *parent );

like, copy that exactly, don't @ me 💅

---

🎀 ARGUMENTS 🎀

• cl — -- undescribed -- 🙈 (yes bestie, the manpage really does just leave it blank, I'm not hiding anything from you fr fr)
• fn — -- undescribed -- 😭
• wq — -- undescribed -- 💀
• parent — -- undescribed -- 🦋

no cap, all four of these are literally listed as -- undescribed -- in the source page. iconic of them to leave us hanging, but that's the lore and I'm not inventing backstory 🌈

---

🔥 DESCRIPTION 🔥

Typically used when running out of one closure, and we want to run fn asynchronously out of a new closure — parent will then wait for cl to finish ⭐

so like: you're already inside a closure, you want fn to go do its thing asynchronously in a shiny new closure, and then parent parks itself and waits for cl to wrap up. main character energy, honestly 👑

---

🦋 SEE ALSO 🦋

Kernel file ./include/linux/closure.h — go read the header, it's the whole vibe iykyk 📖

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

---

and that's the whole page bestie, slay 💖 this one lives in ./include/linux, dated October 2026, and it's closure_call(9) — periodt 🎀✨