From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-io: fix EOF Ctrl-D handling in qemu-io readline code
Date: Fri, 8 Dec 2017 13:35:20 +0000 [thread overview]
Message-ID: <20171208133520.GF11767@redhat.com> (raw)
In-Reply-To: <20171208121521.GA2458@work-vm>
On Fri, Dec 08, 2017 at 12:15:21PM +0000, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrange (berrange@redhat.com) wrote:
> > 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) {
>
> Personally I'd have made that EOF or 0x4 - but that's fine
I thought about that, but it is impossible to get 'EOF' when the terminal
is in raw mode, so there's little point.
> (I don't see the point of reading the ioctl to figure out which EOF
> char we're using; it seems to turn a trivial check into something much
> more complex)
I'd already done the work to read termios settings by time I read this
comment, so I've sent a v2 anyway :-)
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2017-12-08 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 11:57 [Qemu-devel] [PATCH] qemu-io: fix EOF Ctrl-D handling in qemu-io readline code Daniel P. Berrange
2017-12-06 14:22 ` 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 [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=20171208133520.GF11767@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@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).