From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/3] socket: unlink unix socket on remove
Date: Mon, 27 Jun 2016 09:10:30 +0100 [thread overview]
Message-ID: <20160627081030.GC12067@redhat.com> (raw)
In-Reply-To: <20160624220710.GA8254@redhat.com>
On Sat, Jun 25, 2016 at 01:07:10AM +0300, Michael S. Tsirkin wrote:
> On Fri, Jun 24, 2016 at 02:08:52PM +0200, Marc-André Lureau wrote:
> > On Thu, Jun 23, 2016 at 7:01 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > >> > Maybe what you want is a need_unlink feature.
> > >> > Set it for unix sockets only, that would make some sense.
> > >>
> > >> Oh perhaps what you mean is that if the fd was passed, we should cleanup the unix socket? Yes, I think we should do that then. I'll update the series.
> >
> > Actually it's not possible to pass a listening fd to a socket chardev
> > today (the path argument doesn't understand /dev/fdset), so only path
> > created by qemu will be cleaned up.
> >
> > >
> > > I'd like it better contained - that's all. So let's set a flag that says
> > > "must unlink" as opposed to "it's listening".
> >
> > You suggest to rename QIO_CHANNEL_FEATURE_LISTEN to
> > QIO_CHANNEL_FEATURE_LISTEN_MUST_UNLINK ?
>
> QIO_CHANNEL_FEATURE_UNLINK_ON_CLOSE
>
> or something like this.
>
> Or maybe QIO_CHANNEL_FEATURE_BOUND
>
> > Or to add another feature
> > flag? I don't think that brings anything useful here.
>
> The point is that in the future we might be listening on sockets where
> we did not bind it. I would think that in that case, we do not want to
> unlink it. So name should reflect this somehow.
There is no possibility of listening on sockets without binding to them
with the current design of the code. If & when we want such support we
can adapt as needed, but I don't see any real point in trying to support
something that is impossible right now.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-06-27 8:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 19:28 [Qemu-devel] [PATCH v2 0/3] chardev cleanups marcandre.lureau
2016-06-16 19:28 ` [Qemu-devel] [PATCH v2 1/3] char: clean up remaining chardevs when leaving marcandre.lureau
2016-06-23 9:34 ` Daniel P. Berrange
2016-06-29 10:53 ` Paolo Bonzini
2016-06-29 11:40 ` Marc-André Lureau
2016-06-16 19:28 ` [Qemu-devel] [PATCH v2 2/3] socket: add listen feature marcandre.lureau
2016-06-23 9:35 ` Daniel P. Berrange
2016-06-16 19:28 ` [Qemu-devel] [PATCH v2 3/3] socket: unlink unix socket on remove marcandre.lureau
2016-06-23 4:41 ` Michael S. Tsirkin
2016-06-23 4:51 ` Michael S. Tsirkin
2016-06-23 9:08 ` Marc-André Lureau
2016-06-23 17:01 ` Michael S. Tsirkin
2016-06-24 12:08 ` Marc-André Lureau
2016-06-24 12:13 ` Daniel P. Berrange
2016-06-24 22:07 ` Michael S. Tsirkin
2016-06-27 8:10 ` Daniel P. Berrange [this message]
2016-06-23 9:36 ` Daniel P. Berrange
2016-06-17 12:34 ` [Qemu-devel] [PATCH v2 0/3] chardev cleanups Paolo Bonzini
2016-06-23 9:36 ` Daniel P. Berrange
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=20160627081030.GC12067@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).