n_tty_receive_break(9)

💖 n_tty_receive_break(9) 💖

okay bestie, welcome to the Kernel API Manual entry for n_tty_receive_break — yes, it's giving very niche kernel-core, and we're gonna understand it together 🫶✨

---

🌸 NAME 🌸

n_tty_receive_break — handle break

---

✨ SYNOPSIS ✨

void n_tty_receive_break (struct tty_struct *tty );

---

🎀 ARGUMENTS 🎀

• tty — terminal 💻

---

🦋 DESCRIPTION 🦋

So picture this: an RS232 break event has been hit in the incoming bitstream 😭✨ This can cause a whole variety of events depending upon the termios settings — like, it's not one fixed outcome, the termios config is lowkey the main character here 💅

Locking: n_tty_receive_buf/producer path: caller holds non-exclusive termios_rwsem 🔒

---

⭐ NOTE ⭐

may get exclusive termios_rwsem if flushing input buffer 👀

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/tty/n_tty.c, plus all these iconic neighbors:

• n_tty_kick_worker(9)
• n_tty_write_wakeup(9)
• put_tty_queue(9)
• reset_buffer_flags(9)
• n_tty_flush_buffer(9)
• is_utf8_continuation(9)
• is_continuation(9)
• do_output_char(9)
• process_output(9)
• process_output_block(9)
• __process_echoes(9)
• add_echo_byte(9)
• echo_move_back_col(9)
• echo_set_canon_col(9)
• echo_erase_tab(9)
• echo_char_raw(9)
• echo_char(9)
• finish_erasing(9)
• eraser(9)
• isig(9)
• n_tty_receive_overrun(9)
• n_tty_receive_parity_error(9)
• n_tty_receive_char_flow_ctrl(9)
• n_tty_receive_char(9)
• n_tty_receive_buf_common(9)
• n_tty_set_termios(9)
• n_tty_close(9)
• n_tty_open(9)
• copy_from_read_buf(9)
• canon_copy_from_read_buf(9)
• job_control(9)
• n_tty_read(9)
• n_tty_write(9)
• n_tty_poll(9)
• n_tty_inherit_ops(9)

---

and that's the whole vibe check, bestie — source path ./drivers/tty, date October 2026, periodt 💅🎀🫶