tty_ldisc_receive_buf(9)

💖 tty_ldisc_receive_buf 💖

okay bestie, so we're in the Kernel API Manual today and the star of the show is tty_ldisc_receive_buf — literally the function that forwards data to the line discipline. no cap, that's the whole vibe. 🎀

---

✨ NAME ✨

tty_ldisc_receive_buf — forward data to line discipline 🦋

---

🌸 SYNOPSIS 🌸

size_t tty_ldisc_receive_buf (struct tty_ldisc *ld , const u8 *p , const
       const u8 *f , size_t count );

wait — copy that exactly, ok? the line break and all. she's precise. 💅

---

💜 ARGUMENTS 💜

• ld — the line discipline that's gonna process the input. she's the one doing the work, periodt. 👑
• p — char buffer. the actual bytes, living their life. 🍓
• f — the flags buffer: TTY_NORMAL, TTY_BREAK, etc. think of it as the little mood ring for each byte. 🌈
• count — number of bytes to process. how many we're serving today, no more no less. ✨

---

🧚 DESCRIPTION 🧚

here's the tea: if you're a caller other than flush_to_ldisc, you need to exclude the kworker from concurrent use of the line discipline. yes, really. don't let them both touch it at once, that's giving chaos energy 😭. and if you want to see how it's done properly, go look at paste_selection — she ate. 💅

bestie pls don't skip this part. the kworker exclusion is not optional vibes, it's the whole point. 🙈

---

⭐ RETURN ⭐

returns the number of bytes processed. iconic. 🔥

---

🌟 SEE ALSO 🌟

• Kernel file ./drivers/tty/tty_buffer.c
• 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_flush(9)
• __tty_buffer_request_room(9)
• tty_prepare_flip_string(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)

the whole friend group, fr fr. go say hi. 🫶

---

k bye ily, this page came straight out of ./drivers/tty and it's dated October 2026 — so yes, she's from the future and she's still slaying 💀✨