wait_for_completion(9)

✨ wait_for_completion — bestie, let's wait for a task to finish ✨

okay so real quick, before anything else: you're reading the wait_for_completion(9) page from the Kernel API Manual 💅 (yes we're in kernel-land, yes it's giving main character energy, stay with me).

---

🌸 NAME 🌸

wait_for_completion — waits for completion of a task 🎀

---

🦋 SYNOPSIS 🦋

void wait_for_completion (struct completion *x );

---

💖 ARGUMENTS 💖

• x — holds the state of this particular completion. it's literally the little bookkeeper of your waiting arc, no cap 📖✨

---

🔥 DESCRIPTION 🔥

So this one waits to be signaled for completion of a specific task. That's the whole vibe. You call it, you wait, somebody signals you, you're done. slay 🫶

⚠️ But hear me loud and clear: it is NOT interruptible and there is no timeout. None. Zero. It's gonna wait however long it takes, and you're just gonna sit there. It's giving "held hostage by scheduling" energy 😭💀 Not a single escape hatch. Plan accordingly.

Also pls go look at the similar routines (i.e. wait_for_completion_timeout) — those come with timeout and interrupt capability, which is lowkey the upgrade you might actually want. Also see complete. 👑

---

🌈 SEE ALSO 🌈

Kernel file ./kernel/sched/completion.c, plus the whole friend group:

• complete(9)
• complete_all(9)
• wait_for_completion_timeout(9)
• wait_for_completion_io(9)
• wait_for_completion_io_timeout(9)
• wait_for_completion_interruptible(9)
• wait_for_completion_interruptible_timeout(9)
• wait_for_completion_killable(9)
• wait_for_completion_killable_timeout(9)
• try_wait_for_completion(9)
• completion_done(9)

---

okay that's the whole page, you ate that 💅✨

sign-off szn: this little gem lives over at ./kernel/sched, stamped October 2026, and it's wait_for_completion(9) forever and always 🎀🦋🌸 go wait on something, bestie 🫶