nbcon_context_can_proceed(9)

💅 nbcon_context_can_proceed(9) ✨

Okay bestie, welcome to the Kernel API Manual — this one's a little function with big main character energy, and honestly it's giving "am I still the lock owner or not" vibes. Let's get into it 🎀

---

🌸 NAME 🌸

nbcon_context_can_proceed — check whether ownership can proceed 🫶

---

✨ SYNOPSIS ✨

bool nbcon_context_can_proceed (struct nbcon_context *ctxt , struct
       nbcon_state *cur );

---

🦋 ARGUMENTS 🦋

• ctxt — the nbcon context you got from nbcon_context_try_acquire 💖
• cur — the current console state, like, right now 👑

---

💀 RETURN 💀

Returns True if this context still owns the console. Returns False if ownership was handed over or taken — i.e. somebody else is main character now 😭

---

🔥 DESCRIPTION 🔥

Okay so, real talk: you must invoke this when you're entering the unsafe state, so you can make sure it still owns the lock. No cap. 💅

You also must invoke it when you're exiting the unsafe context, so the lock can eventually be freed for a higher priority context that asked for the friendly handover. Be nice, share the console 🫶

It can be called inside an unsafe section when the console is just temporary in safe state, instead of exiting and entering the unsafe state. Convenient, honestly ✨

It can also be called in the safe context before doing an expensive safe operation. Like, why would you do the operation when a higher priority context took the lock? That'd be such a waste, ngl 🥲

⚠️ BIG ONE, bestie: when this function returns false, the calling context no longer owns the console and is no longer allowed to go forward. Periodt. In this case it must back out immediately and carefully 😭 The buffer content is also no longer trusted, since it no longer belongs to the calling context. Do not touch. Do not trust. Back away slowly 💀

---

🌈 SEE ALSO 🌈

Kernel file ./kernel/printk/nbcon.c — and the whole friend group:

• nbcon_state_set(9)
• nbcon_state_read(9)
• nbcon_state_try_cmpxchg(9)
• nbcon_seq_read(9)
• nbcon_seq_force(9)
• nbcon_seq_try_update(9)
• nbcon_context_try_acquire_direct(9)
• nbcon_context_try_acquire_requested(9)
• nbcon_context_try_acquire_handover(9)
• nbcon_context_try_acquire_hostile(9)
• nbcon_context_try_acquire(9)
• nbcon_context_release(9)
• nbcon_can_proceed(9)
• __nbcon_context_update_unsafe(9)
• nbcon_enter_unsafe(9)
• nbcon_exit_unsafe(9)
• nbcon_reacquire_nobuf(9)
• nbcon_emit_next_record(9)
• nbcon_kthread_should_wakeup(9)
• nbcon_kthread_func(9)
• nbcon_irq_work(9)
• nbcon_kthreads_wake(9)
• nbcon_kthread_create(9)
• nbcon_get_cpu_emergency_nesting(9)
• nbcon_get_default_prio(9)
• nbcon_allow_unsafe_takeover(9)
• nbcon_legacy_emit_next_record(9)
• __nbcon_atomic_flush_pending_con(9)
• nbcon_atomic_flush_pending_con(9)
• __nbcon_atomic_flush_pending(9)
• nbcon_atomic_flush_pending(9)
• nbcon_atomic_flush_unsafe(9)
• nbcon_cpu_emergency_enter(9)
• nbcon_cpu_emergency_exit(9)
• nbcon_alloc(9)
• nbcon_free(9)
• nbcon_device_try_acquire(9)
• nbcon_device_release(9)
• nbcon_kdb_try_acquire(9)
• nbcon_kdb_release(9)
• nbcon_write_context_is_braille(9)
• nbcon_braille_try_acquire(9)
• nbcon_braille_release(9)

---

And that's the whole thing, bestie 🧚 This page lives under ./kernel/printk, dated October 2026 — slay, go forth and check your ownership before you proceed 💜💅