From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Egmont Koblinger <egmont@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Data corruption when pasting large data to terminal
Date: Fri, 17 Feb 2012 20:28:25 +0100 [thread overview]
Message-ID: <20120217192825.GE2707@elf.ucw.cz> (raw)
In-Reply-To: <20120216005437.GA22858@kroah.com>
Hi!
> > Sorry, I didn't emphasize the point that makes me suspect it's a kernel issue:
> >
> > - strace reveals that the terminal emulator writes the correct data
> > into /dev/ptmx, and the kernel reports no short writes(!), all the
> > write(..., ..., 68) calls actually return 68 (the length of the
> > example file's lines incl. newline; I'm naively assuming I can trust
> > strace here.)
> > - strace reveals that the receiving application (bash) doesn't receive
> > all the data from /dev/pts/N.
> > - so: the data gets lost after writing to /dev/ptmx, but before
> > reading it out from /dev/pts/N.
>
> Which it will, if the reader doesn't read fast enough, right? Is the
> data somewhere guaranteed to never "overrun" the buffer? If so, how do
> we handle not just running out of memory?
Start blocking the writer?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2012-02-17 19:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGWcZkJs2uQHM=7wmf1JOLmUeS3Mxo5L4arMuMQSez1mvJLKQA@mail.gmail.com>
2012-02-15 18:50 ` Egmont Koblinger
2012-02-15 23:30 ` Greg KH
2012-02-16 0:39 ` Egmont Koblinger
2012-02-16 0:54 ` Greg KH
2012-02-16 1:12 ` Egmont Koblinger
2012-02-17 19:28 ` Pavel Machek [this message]
2012-02-17 21:57 ` Bruno Prémont
2012-02-19 20:55 ` Egmont Koblinger
2012-02-19 21:14 ` Bruno Prémont
2012-02-19 21:35 ` Alan Cox
2012-02-19 21:41 ` Egmont Koblinger
2012-02-20 17:18 ` Egmont Koblinger
2012-02-20 17:31 ` Pavel Machek
2012-02-20 21:11 ` Egmont Koblinger
2012-02-20 21:29 ` Egmont Koblinger
2012-02-15 23:58 ` Parag Warudkar
2012-02-16 0:10 ` Greg KH
2012-02-16 11:42 ` Egmont Koblinger
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=20120217192825.GE2707@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=egmont@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®