From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] io: ensure UNIX client doesn't unlink server socket
Date: Mon, 14 Jan 2019 13:49:53 -0600 [thread overview]
Message-ID: <aa15d9b9-11ff-a21e-6ecb-ef73fcc7687a@redhat.com> (raw)
In-Reply-To: <20190114113827.24388-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
On 1/14/19 5:38 AM, Daniel P. Berrangé wrote:
> The qio_channel_socket_close method for was mistakenly unlinking the
> UNIX server socket, even if the channel was a client connection. This
> was not noticed with chardevs, since they never call close, but with the
> VNC server, this caused the VNC server socket to be deleted after the
> first client quit.
>
> The qio_channel_socket_close method also needlessly reimplemented the
> logic that already exists in socket_listen_cleanup(). Just call that
> method directly, for listen sockets only.
>
> This fixes a regression introduced in QEMU 3.0.0 with
>
> commit d66f78e1eaa832f73c771d9df1b606fe75d52a50
> Author: Pavel Balaev <mail@void.so>
> Date: Mon May 21 19:17:35 2018 +0300
>
> Delete AF_UNIX socket after close
>
> Fixes launchpad #1795100
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> io/channel-socket.c | 19 ++------
> tests/test-io-channel-socket.c | 86 ++++++++++++++++++++++++++++++----
> 2 files changed, 80 insertions(+), 25 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-01-14 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 11:38 [Qemu-devel] [PATCH] io: ensure UNIX client doesn't unlink server socket Daniel P. Berrangé
2019-01-14 19:49 ` Eric Blake [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aa15d9b9-11ff-a21e-6ecb-ef73fcc7687a@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).