nbcon_exit_unsafe(9)

💅 nbcon_exit_unsafe — bestie's guide to leaving the unsafe zone

okay so this is nbcon_exit_unsafe(9) from the Kernel API Manual, and it's literally the "okay i'm done being unsafe, can i keep the console pls" check. let's get into it 🎀

---

✨ NAME ✨

nbcon_exit_unsafe — Exit an unsafe region in the driver 🦋

---

🌸 SYNOPSIS 🌸

bool nbcon_exit_unsafe (struct nbcon_write_context *wctxt );

like, it takes one thing and gives you back a bool. simple. iconic. no notes 💅

---

🎀 ARGUMENTS 🎀

• wctxt — the write context that was handed to the write function. that's the lil baton you got passed, bestie 🫶

---

⭐ RETURN ⭐

• True — this context still owns the console. congrats, it's yours, keep going king 👑
• False — ownership was handed over or taken. yikes. more on that below 😭

---

💖 DESCRIPTION 💖

so. when this function returns false, the calling context no longer owns the console and is no longer allowed to go forward. that's not a suggestion, that's the vibe check failing. in that case it must back out immediately and carefully — like, do not pass go, do not keep printing 😭

also, the buffer content is no longer trusted, since it no longer belongs to the calling context. someone else's console, someone else's buffer. hands off. 🙈

fr fr: false means back out immediately and carefully, and stop trusting the buffer. no cap. 💀

---

🦋 SEE ALSO 🦋

the whole friend group lives in the kernel file ./kernel/printk/nbcon.c:

• 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_context_can_proceed(9)
• nbcon_can_proceed(9)
• __nbcon_context_update_unsafe(9)
• nbcon_enter_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)

---

that's the whole page, bestie, go forth and exit your unsafe regions responsibly 💜✨ this was nbcon_exit_unsafe(9) from the Kernel API Manual, straight out of ./kernel/printk, dated October 2026 — slay, and see you in the next manpage 🧚🌈