tty_buffer_flush(9)

💅 NAME 💅

okay so bestie, this is tty_buffer_flush(9) from the Kernel API Manual, and it does exactly what it says on the label: flush full tty buffers ✨

---

🌸 SYNOPSIS 🌸

it’s giving this exact signature, no cap:

void tty_buffer_flush (struct tty_struct *tty , struct tty_ldisc *ld );

---

🎀 ARGUMENTS 🎀

• tty — the tty you’re flushing, bestie 💖
• ld — optional ldisc ptr, and it must be referenced 👑

---

🦋 DESCRIPTION 🦋

so this function flushes all the buffers containing receive data. like, every single one holding receive data gets the flush treatment 🌊

if ld != NULL, it flushes the ldisc input buffer too. periodt 💅

Locking: it takes the buffer lock to ensure a single-threaded flip buffer 'consumer' 🔒 no chaotic multi-threaded flip-buffer consumer energy allowed, iykyk.

---

💖 SEE ALSO 💖

the kernel file in question is ./drivers/tty/tty_buffer.c, and here’s the whole squad of related functions, all iconic, all (9):

• tty_buffer_lock_exclusive(9)
• tty_buffer_unlock_exclusive(9)
• tty_buffer_space_avail(9)
• tty_buffer_free_all(9)
• tty_buffer_alloc(9)
• tty_buffer_free(9)
• __tty_buffer_request_room(9)
• tty_prepare_flip_string(9)
• tty_ldisc_receive_buf(9)
• flush_to_ldisc(9)
• tty_flip_buffer_push(9)
• tty_insert_flip_string_and_push_buffer(9)
• tty_buffer_init(9)
• tty_buffer_set_limit(9)

---

and that’s the whole cute little page, bestie 🫶 it lives under ./drivers/tty, the date stamp is October 2026, and the page is literally tty_buffer_flush(9) — slay, bye 💋✨