From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40886) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cYZ4v-0000fB-GW for qemu-devel@nongnu.org; Tue, 31 Jan 2017 09:06:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cYZ4r-00044R-KM for qemu-devel@nongnu.org; Tue, 31 Jan 2017 09:06:37 -0500 Received: from mx4-phx2.redhat.com ([209.132.183.25]:49832) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cYZ4r-000449-Bu for qemu-devel@nongnu.org; Tue, 31 Jan 2017 09:06:33 -0500 Date: Tue, 31 Jan 2017 09:06:32 -0500 (EST) From: =?utf-8?Q?Marc-Andr=C3=A9?= Lureau Message-ID: <421566746.771522.1485871592528.JavaMail.zimbra@redhat.com> In-Reply-To: <1485870329-79428-1-git-send-email-eswierk@skyportsystems.com> References: <1485870329-79428-1-git-send-email-eswierk@skyportsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] char: drop data written to a disconnected pty List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ed Swierk Cc: qemu-devel@nongnu.org, libvir-list@redhat.com, berrange@redhat.com, pbonzini@redhat.com, marcandre lureau , eblake@redhat.com, ben@skyportsystems.com Hi ----- Original Message ----- > When a serial port writes data to a pty that's disconnected, drop the > data and return the length dropped. This avoids triggering pointless > retries in callers like the 16550A serial_xmit(), and causes > qemu_chr_fe_write() to write all data to the log file, rather than > logging only while a pty client like virsh console happens to be > connected. > > Signed-off-by: Ed Swierk > --- > qemu-char.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/qemu-char.c b/qemu-char.c > index 676944a..ccb6923 100644 > --- a/qemu-char.c > +++ b/qemu-char.c > @@ -1528,7 +1528,7 @@ static int pty_chr_write(CharDriverState *chr, const > uint8_t *buf, int len) > /* guest sends data, check for (re-)connect */ > pty_chr_update_read_handler_locked(chr); > if (!s->connected) { > - return 0; > + return len; I think this can be confusing if some backends silently drop the data (under disconnected state), while other don't. Perhaps we should have instead a new common chardev property "hup-drop" ? (suggestions for better name welcome) > } > } > return io_channel_send(s->ioc, buf, len); > -- > 1.9.1 > >