From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: "Daniel P. Berrange" <berrange@redhat.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: Sat, 25 Jun 2016 01:07:10 +0300 [thread overview]
Message-ID: <20160624220710.GA8254@redhat.com> (raw)
In-Reply-To: <CAJ+F1CLu9LidBh3x-wWdtoqWt5gaaiw3McJQMGCbfTbYJwYMaQ@mail.gmail.com>
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.
> What would you think Daniel?
>
> --
> Marc-André Lureau
next prev parent reply other threads:[~2016-06-24 22:07 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 [this message]
2016-06-27 8:10 ` Daniel P. Berrange
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=20160624220710.GA8254@redhat.com \
--to=mst@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.