From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=36192 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PxZ48-0003e6-Hb for qemu-devel@nongnu.org; Thu, 10 Mar 2011 01:09:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PxZ47-0007eG-CE for qemu-devel@nongnu.org; Thu, 10 Mar 2011 01:09:40 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49140) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PxZ47-0007dx-1i for qemu-devel@nongnu.org; Thu, 10 Mar 2011 01:09:39 -0500 From: Amit Shah Date: Thu, 10 Mar 2011 11:39:19 +0530 Message-Id: <0f35b89ae35e35afa8499f8016900ace82bc86a5.1299737220.git.amit.shah@redhat.com> In-Reply-To: References: In-Reply-To: References: Subject: [Qemu-devel] [PULL (resend, rebase) 5/5] virtio-serial: Don't clear ->have_data() pointer after unplug List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Amit Shah , qemu list After a port unplug operation, the port->info->have_data() pointer was set to NULL. The problem is, the ->info struct is shared by all ports, effectively disabling writes to other ports. Reported-by: juzhang Signed-off-by: Amit Shah --- hw/virtio-console.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/hw/virtio-console.c b/hw/virtio-console.c index 699f190..0bf35ef 100644 --- a/hw/virtio-console.c +++ b/hw/virtio-console.c @@ -82,7 +82,6 @@ static int virtconsole_exitfn(VirtIOSerialPort *port) VirtConsole *vcon = DO_UPCAST(VirtConsole, port, port); if (vcon->chr) { - port->info->have_data = NULL; qemu_chr_close(vcon->chr); } -- 1.7.4