qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	Max Reitz <mreitz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH] qemu-io: fix EOF Ctrl-D handling in qemu-io readline code
Date: Wed,  6 Dec 2017 11:57:26 +0000	[thread overview]
Message-ID: <20171206115726.5237-1-berrange@redhat.com> (raw)

qemu-io puts the TTY into non-canonical mode, which means no EOF processing is
done and thus getchar() will never return the EOF constant. Instead we have to
check for an explicit Ctrl-D, aka  0x4, to detect EOF and exit the qemu-io
shell. This fixes the regression that prevented Ctrl-D from triggering an exit
of qemu-io that has existed since readline was first added in

  commit 0cf17e181798063c3824c8200ba46f25f54faa1a
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   Thu Nov 14 11:54:17 2013 +0100

    qemu-io: use readline.c

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---
 qemu-io.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/qemu-io.c b/qemu-io.c
index c70bde3eb1..2ea0bfbaf8 100644
--- a/qemu-io.c
+++ b/qemu-io.c
@@ -322,7 +322,9 @@ static char *fetchline_readline(void)
     readline_start(readline_state, get_prompt(), 0, readline_func, &line);
     while (!line) {
         int ch = getchar();
-        if (ch == EOF) {
+        /* In non-canon tty mode we get 0x4 (Ctrl-D), not the stdio "EOF"
+         * constant */
+        if (ch == 0x4) {
             break;
         }
         readline_handle_byte(readline_state, ch);
-- 
2.14.3

             reply	other threads:[~2017-12-06 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 11:57 Daniel P. Berrange [this message]
2017-12-06 14:22 ` [Qemu-devel] [PATCH] qemu-io: fix EOF Ctrl-D handling in qemu-io readline code Eric Blake
2017-12-06 14:25   ` Daniel P. Berrange
2017-12-06 14:30     ` Eric Blake
2017-12-06 16:14       ` Markus Armbruster
2017-12-08 12:15 ` Dr. David Alan Gilbert
2017-12-08 13:35   ` Daniel P. Berrange

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=20171206115726.5237-1-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).