n_tty_receive_overrun(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… n_tty_receive_overrun(9) β€” a Kernel API Manual moment

okay bestie, so this one lives in the Kernel API Manual and it's called n_tty_receive_overrun, and honestly? it's giving "the cleanup crew of the tty world." let's get into it ✨


🌸 NAME 🌸

n_tty_receive_overrun β€” handle overrun reporting 🫢


✨ SYNOPSIS ✨

void n_tty_receive_overrun (const struct tty_struct *tty );

that's it. one function, one arg, zero drama. iconic.


πŸŽ€ ARGUMENTS πŸŽ€

  • tty β€” the terminal πŸ’» (that's literally what it is, no cap)

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so picture this: data arrived faster than we could process it. the tty driver has already flagged that this happened, but β€” and this is the heartbreaking part β€” the bits that were missed are gone forever. 😭 not "recoverable later," not "in a buffer somewhere," just poof. bestie, they're not coming back.

this function gets called from the receive_buf path, which means it's single threaded β€” so it's lowkey chilling, it does not need locking, because num_overrun and overrun_time are function private. nobody else is touching them, so we don't have to fight over them. slay. πŸ™ˆ

tl;dr: overrun happened, the data's gone, we report it, we move on. main character energy. πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

that's the whole group chat, fr fr. go read them all, iykyk πŸ§šπŸ’œ


gentle reminder bestie: once those bits are missed, they are missed. there is no undo. guard your throughput accordingly πŸ’€

and that's the whole page! this lil cutie came from ./drivers/tty, dated October 2026 πŸŒˆπŸ¦‹ mwah, go read the source, ily, bye! πŸ’–β­

πŸ“¦ where this page comes from