| commit | 5a693efda84d7df5136cc2bd31c959bb1530b0c9 | |
| author | Gonglei <arei.gonglei@huawei.com> | |
| Fri, 8 Jul 2016 03:37:36 +0000 (8 11:37 +0800) | ||
| committer | Gerd Hoffmann <kraxel@redhat.com> | |
| Tue, 12 Jul 2016 06:34:13 +0000 (12 08:34 +0200) | ||
| tree | 79d2368f261ef83d1efbf5fa4e3f66fb1aec47cc | treesnapshot (tar.gz zip) |
| parent | f1ef55786691a1bf79db0b74ba1e5347a0d38c1b | commitdiff |
vnc: fix incorrect checking condition when updating client
vs->disconnecting is set to TRUE and vs->ioc is closed, but
vs->ioc isn't set to NULL, so that the vnc_disconnect_finish()
isn't invoked when you update client in vnc_update_client()
after vnc_disconnect_start invoked. Let's using change the checking
condition to avoid resource leak.
Signed-off-by: Haibin Wang <wanghaibin.wang@huawei.com>
Signed-off-by: Gonglei <arei.gonglei@huawei.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 1467949056-81208-1-git-send-email-arei.gonglei@huawei.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
vs->disconnecting is set to TRUE and vs->ioc is closed, but
vs->ioc isn't set to NULL, so that the vnc_disconnect_finish()
isn't invoked when you update client in vnc_update_client()
after vnc_disconnect_start invoked. Let's using change the checking
condition to avoid resource leak.
Signed-off-by: Haibin Wang <wanghaibin.wang@huawei.com>
Signed-off-by: Gonglei <arei.gonglei@huawei.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Message-id: 1467949056-81208-1-git-send-email-arei.gonglei@huawei.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
| ui/vnc.c | diffblobblamehistory |