nbcon_conte...re_requested(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nbcon_conte...re_requested — the Kernel API Manual, bestie edition ✨

okay so this page is from the Kernel API Manual and it's about nbcon_context_try_acquire_requested, which lowkey is the "you asked nicely, now let's see if you actually get it" function 🫶

✨ NAME ✨

nbcon_context_try_acquire_requested — bestie, this is the "try to acquire after having requested a handover" one 💖

🦋 SYNOPSIS 🦋

int nbcon_context_try_acquire_requested (struct nbcon_context *ctxt ,
       struct nbcon_state *cur );

🎀 ARGUMENTS 🎀

  • ctxt — the context of the caller, aka you, the one asking 🫵
  • cur — the current console state, the vibe check of the console rn ✨

🌸 DESCRIPTION 🌸

okay so picture this: this is a helper function for nbcon_context_try_acquire_handover — it's literally the sidekick 🤝 It gets called when the console is in an unsafe state. The way it works is the current owner will release the console on exit from the unsafe region. so it's giving "I'm leaving the group chat, the key is on the table" energy 💅

Errors (aka the ways this can go wrong, and bestie there are two 😭):

  • -EPERM — either a panic is in progress and this is not the panic CPU, or this context is no longer the waiter. so rude 🙈
  • -EBUSY — the console is still locked. the caller should continue waiting. yes we're in the queue, no it's not moving, stay seated 🪑

👑 RETURN 👑

0 on success — and hey, cur gets updated to the new console state, slay ✨ Otherwise you get an error code on failure. no cap.

💀 NOTE 💀

⚠️ important caveat bestie: the caller must still remove the request when an error has occurred — except when this context is no longer the waiter. that exception is the whole plot twist, don't forget it 🙈

🌈 SEE ALSO 🌈

Kernel file ./kernel/printk/nbcon.c — and honestly the whole friend group is here, iykyk 💜

🌸 okay that's the whole page, you ate that 🍓 this lil gem lives in ./kernel/printk, dated October 2026, periodt 💅✨

📦 where this page comes from