public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Peterson <joe@skyrush.com>
To: Greg KH <gregkh@suse.de>
Cc: Artur Skawina <art.08.09@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Moving tty->stopped logic to ldisc (pty: fix data loss when stopped (^S/^Q))
Date: Tue, 11 Aug 2009 13:00:10 -0600	[thread overview]
Message-ID: <4A81BFBA.1070507@skyrush.com> (raw)
In-Reply-To: <20090811185221.GA4750@suse.de>

Greg KH wrote:
> On Tue, Aug 11, 2009 at 12:16:39PM -0600, Joe Peterson wrote:
>> [Please include my email address in replies]
>>
>> Hi all,
>>
>> This is in regard to the problem that the recent patch ("pty: fix data
>> loss when stopped (^S/^Q)") fixes.  The issue is something I've been
>> looking at recently as well after noticing (I noticed it first as loss
>> of echoes, since I was re-testing what my echo buffer code originally
>> fixed).
> 
> Hm, is this resolved by git id 85dfd81dc57e8183a277ddd7a56aa65c96f3f487
> that Linus commited to the tree yesterday?

Well, that patch "fixes" the issue of the lost chars in that it resumes
previous behavior, but it does not address the two points I mentioned in
this post - ones that are hard to fix without moving checks for
tty->stopped to the ldisc or somehow locking the state of tty->stopped
(which seems a bit scary).  In other words, there still exist windows
for loss of chars.

						-Joe

      reply	other threads:[~2009-08-11 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 18:16 Moving tty->stopped logic to ldisc (pty: fix data loss when stopped (^S/^Q)) Joe Peterson
2009-08-11 18:52 ` Greg KH
2009-08-11 19:00   ` Joe Peterson [this message]

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=4A81BFBA.1070507@skyrush.com \
    --to=joe@skyrush.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=art.08.09@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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