diff options
author | Daniel P. Berrangé <berrange@redhat.com> | 2018-06-04 13:30:43 +0100 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2018-06-28 19:05:30 +0200 |
commit | 1507bd136fd9a516226fce8738d361a64f45b699 (patch) | |
tree | a159e1edc95f6da87b90c40ce5f43673c3e30026 /chardev | |
parent | 8bca9a03ec60d63b2ee6a959fe85dda4206811e0 (diff) | |
download | qemu-1507bd136fd9a516226fce8738d361a64f45b699.zip qemu-1507bd136fd9a516226fce8738d361a64f45b699.tar.gz qemu-1507bd136fd9a516226fce8738d361a64f45b699.tar.bz2 |
chardev: don't splatter terminal settings on exit if not previously set
The stdio chardev finalize method calls term_exit() to restore the
original terminal settings that were saved in the "oldtty" global. If
the qemu_chr_open_stdio() method exited with an error, we might not have
any original terminal settings saved in "oldtty" yet.
eg
$ qemu-system-x86_64 -monitor stdio -daemonize
qemu-system-x86_64: -monitor stdio: cannot use stdio with -daemonize
will cause QEMU to splatter the terminal settings with an all-zeros
"struct termios", with predictably unpleasant results. Fortunately the
existing "stdio_in_use" flag is suitable witness for whether "oldtty"
contains settings that need restoring.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20180604123043.13985-1-berrange@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'chardev')
-rw-r--r-- | chardev/char-stdio.c | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/chardev/char-stdio.c b/chardev/char-stdio.c index 96375f2..9624220 100644 --- a/chardev/char-stdio.c +++ b/chardev/char-stdio.c @@ -46,8 +46,10 @@ static bool stdio_echo_state; static void term_exit(void) { - tcsetattr(0, TCSANOW, &oldtty); - fcntl(0, F_SETFL, old_fd0_flags); + if (stdio_in_use) { + tcsetattr(0, TCSANOW, &oldtty); + fcntl(0, F_SETFL, old_fd0_flags); + } } static void qemu_chr_set_echo_stdio(Chardev *chr, bool echo) |