From: "Mockern" <Mockern@yandex.ru>
To: linux-kernel@vger.kernel.org
Subject: buffer overflows in the tty flip buffer in 2.6.17
Date: Sat, 17 Feb 2007 15:29:31 +0300 (MSK) [thread overview]
Message-ID: <45D6F52B.000003.10185@webmail19.yandex.ru> (raw)
When data is received from the hardware, it needs to be placed into the tty device's flip buffer. This can be done with the following bit of code:
for (i = 0; i < data_size; ++i) {
if (tty->flip.count >= TTY_FLIPBUF_SIZE)
tty_flip_buffer_push(tty);
tty_insert_flip_char(tty, data[i], 0);
}
tty_flip_buffer_push(tty);
This example makes sure there are no buffer overflows in the tty flip buffer as the data is being added.
But how it is done in 2.6.17 linux kernel? I did check this "overflow code" in new tty driver's code. This code looks like just removed. But somehow overflow in the tty buffer must be kept.
next reply other threads:[~2007-02-17 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 12:29 Mockern [this message]
2007-02-17 13:14 ` buffer overflows in the tty flip buffer in 2.6.17 Jiri Slaby
2007-02-17 15:17 ` Lennart Sorensen
2007-02-17 15:52 ` Mockern
2007-02-17 16:10 ` Lennart Sorensen
2007-02-19 20:19 ` Alan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45D6F52B.000003.10185@webmail19.yandex.ru \
--to=mockern@yandex.ru \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox