From: Karl Dahlke <eklhad@comcast.net>
To: mpatocka@redhat.com, peter@hurleysoftware.com
Cc: gregkh@linuxfoundation.org, jslaby@suse.cz, linux-kernel@vger.kernel.org
Subject: [PATCH 3.12] Broken terminal due to echo bufferring
Date: Tue, 10 Dec 2013 05:52:32 -0500 [thread overview]
Message-ID: <20131110055232.eklhad@comcast.net> (raw)
In-Reply-To: alpine.LRH.2.02.1312092103290.11182@file01.intranet.prod.int.rdu2.redhat.com
Just a followup to my last post.
You don't need to compile the write("prompt>") program to see the bug.
Just edit a modest text file with /bin/ed, which runs in cooked mode.
As soon as the file comes up, hit ^c.
Lots of old stuff comes spewing out.
Eventually the tty is back and you can edit the file as usual, or quit.
Karl Dahlke
next prev parent reply other threads:[~2013-12-10 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 2:55 [PATCH 3.12] Broken terminal due to echo bufferring Mikulas Patocka
2013-12-09 4:26 ` Karl Dahlke
2013-12-09 15:43 ` Peter Hurley
2013-12-09 22:18 ` Mikulas Patocka
2013-12-10 0:01 ` Peter Hurley
2013-12-10 2:29 ` Mikulas Patocka
2013-12-10 10:48 ` Karl Dahlke
2013-12-10 11:00 ` Peter Hurley
2013-12-10 10:52 ` Karl Dahlke [this message]
2013-12-10 14:34 ` Peter Hurley
2013-12-11 16:29 ` Mikulas Patocka
2013-12-13 21:24 ` Peter Hurley
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=20131110055232.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=peter@hurleysoftware.com \
/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