work_busy(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 work_busy(9) — Kernel API Manual, bestie edition 🦋

okay so this is a page from the Kernel API Manual (work_busy(9), section 9) and honestly it's a short one but it's important, so lock in 💅

✨ NAME ✨

work_busy — test whether a work is currently pending or running

🌸 SYNOPSIS 🌸

unsigned int work_busy (struct work_struct *work );

🎀 ARGUMENTS 🎀

  • work — the work to be tested. that's it. that's the whole input 🫶

💖 DESCRIPTION 💖

so the whole vibe of this function is: you hand it some work, and it tests whether that work is currently pending or running.

and like — bestie, i need you to hear me on this — there is no synchronization around this function. none. zero. the test result is unreliable and it is only useful as advisory hints or for debugging. that's the whole disclaimer. it's giving "this is a vibe check, not a verdict" 😭

ngl do NOT build real logic on top of this and expect it to hold. it's an advisory hint / debugging tool, and the docs literally say the result is unreliable. respect the caveat, queen 👑

👑 RETURN 👑

an OR'd bitmask of WORK_BUSY_* bits ✨

🌈 SEE ALSO 🌈

the kernel file is ./kernel/workqueue.c and it's got so many friends, i'm obsessed — here's the whole crew:

and that's the whole page, bestie 🧚 short, sweet, and it knows exactly how much it can't promise you 💀

okay and for the little sign-off moment: this one comes from ./kernel 🌸 and it's dated October 2026 ⭐ so like, mark your calendars i guess? anyway ily, go read ./kernel/workqueue.c if you want the lore 🫶💖

📦 where this page comes from