[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 3/3] char-socket: Lock tcp_chr_disconnect() and
From: |
Alberto Garcia |
Subject: |
Re: [Qemu-devel] [PATCH 3/3] char-socket: Lock tcp_chr_disconnect() and socket_reconnect_timeout() |
Date: |
Fri, 08 Feb 2019 10:34:53 +0100 |
User-agent: |
Notmuch/0.18.2 (http://notmuchmail.org) Emacs/24.4.1 (i586-pc-linux-gnu) |
On Thu 07 Feb 2019 03:26:49 PM CET, Daniel P. Berrangé wrote:
>> @@ -457,11 +469,12 @@ static void tcp_chr_disconnect(Chardev *chr)
>> }
>> update_disconnected_filename(s);
>> if (emit_close) {
>> - qemu_chr_be_event(chr, CHR_EVENT_CLOSED);
>> + qemu_idle_add(tcp_chr_be_event_closed, chr, chr->gcontext);
>
> I'm a little concerned that this change might trigger some unexpected
> interactions with the qemu_chr_wait_connected() function. I added some
> more testing around that code, so if it passes the new tests I have in:
>
> https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg05962.html
Forget my previous e-mail, there was a mistake on my side. The test does
pass after rebasing my series on top of that one.
> and also works with the vhostuser reconnect device, then we are
> probably ok.
How do I test this?
Berto
- Re: [Qemu-devel] [PATCH 1/3] main-loop: Don't leak GSources attached to a GMainContext, (continued)
[Qemu-devel] [PATCH 3/3] char-socket: Lock tcp_chr_disconnect() and socket_reconnect_timeout(), Alberto Garcia, 2019/02/07
Re: [Qemu-devel] [PATCH 3/3] char-socket: Lock tcp_chr_disconnect() and socket_reconnect_timeout(), Marc-André Lureau, 2019/02/07
[Qemu-devel] [PATCH 2/3] main-loop: Add qemu_idle_add(), Alberto Garcia, 2019/02/07