qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, stefanha@linux.vnet.ibm.com,
	libvir-list@redhat.com, qemu-devel@nongnu.org,
	lcapitulino@redhat.com, pbonzini@redhat.com, eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH v8 2/7] qapi: Introduce add-fd, remove-fd, query-fdsets
Date: Fri, 10 Aug 2012 18:08:44 +0200	[thread overview]
Message-ID: <5025320C.40206@redhat.com> (raw)
In-Reply-To: <1344564649-6272-3-git-send-email-coreyb@linux.vnet.ibm.com>

Am 10.08.2012 04:10, schrieb Corey Bryant:
> This patch adds support that enables passing of file descriptors
> to the QEMU monitor where they will be stored in specified file
> descriptor sets.
> 
> A file descriptor set can be used by a client like libvirt to
> store file descriptors for the same file.  This allows the
> client to open a file with different access modes (O_RDWR,
> O_WRONLY, O_RDONLY) and add/remove the passed fds to/from an fd
> set as needed.  This will allow QEMU to (in a later patch in this
> series) "open" and "reopen" the same file by dup()ing the fd in
> the fd set that corresponds to the file, where the fd has the
> matching access mode flag that QEMU requests.
> 
> The new QMP commands are:
>   add-fd: Add a file descriptor to an fd set
>   remove-fd: Remove a file descriptor from an fd set
>   query-fdsets: Return information describing all fd sets
> 
> Note: These commands are not compatible with the existing getfd
> and closefd QMP commands.
> 
> Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
> ---
> v5:
>  -This patch is new in v5 and replaces the pass-fd QMP command
>   from v4.
>  -By grouping fds in fd sets, we ease managability with an fd
>   set per file, addressing concerns raised in v4 about handling
>   "reopens" and preventing fd leakage. (eblake@redhat.com,
>   kwolf@redhat.com, dberrange@redhat.com)
> 
> v6
>  -Make @fd optional for remove-fd (eblake@redhat.com)
>  -Make @fdset-id optional for add-fd (eblake@redhat.com)
> 
> v7:
>  -Share fd sets among all monitor connections (kwolf@redhat.com)
>  -Added mon_refcount to keep track of monitor connection count.
> 
> v8:
>  -Add opaque string to add-fd/query-fdsets.
>   (stefanha@linux.vnet.ibm.com)
>  -Use camel case for structures. (stefanha@linux.vnet.ibm.com)
>  -Don't return in-use and refcount from query-fdsets.
>   (stefanha@linux.vnet.ibm.com)
>  -Don't return removed fd's from query-fdsets.
>   (stefanha@linux.vnet.ibm.com)
>  -Use fdset-id rather than fdset_id. (eblake@redhat.com)
>  -Fix fd leak in qmp_add_fd(). (stefanha@linux.vnet.ibm.com)
>  -Update QMP errors. (stefanha@linux.vnet.ibm.com, eblake@redhat.com)
> 
>  monitor.c        |  188 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  qapi-schema.json |   98 ++++++++++++++++++++++++++++
>  qmp-commands.hx  |  117 +++++++++++++++++++++++++++++++++
>  3 files changed, 403 insertions(+)
> 
> diff --git a/monitor.c b/monitor.c
> index 49dccfe..f9a0577 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -140,6 +140,24 @@ struct mon_fd_t {
>      QLIST_ENTRY(mon_fd_t) next;
>  };
>  
> +/* file descriptor associated with a file descriptor set */
> +typedef struct MonFdsetFd MonFdsetFd;
> +struct MonFdsetFd {
> +    int fd;
> +    bool removed;
> +    char *opaque;
> +    QLIST_ENTRY(MonFdsetFd) next;
> +};
> +
> +/* file descriptor set containing fds passed via SCM_RIGHTS */
> +typedef struct MonFdset MonFdset;
> +struct MonFdset {
> +    int64_t id;
> +    int refcount;
> +    QLIST_HEAD(, MonFdsetFd) fds;
> +    QLIST_ENTRY(MonFdset) next;
> +};
> +
>  typedef struct MonitorControl {
>      QObject *id;
>      JSONMessageParser parser;
> @@ -211,6 +229,8 @@ static inline int mon_print_count_get(const Monitor *mon) { return 0; }
>  #define QMP_ACCEPT_UNKNOWNS 1
>  
>  static QLIST_HEAD(mon_list, Monitor) mon_list;
> +static QLIST_HEAD(mon_fdsets, MonFdset) mon_fdsets;
> +static int mon_refcount;

You introduce mon_refcount in this patch and check it against 0 in one
place, but it never gets changed until patch 3 is applied. Would it make
sense to do both in the same patch?

Kevin

  parent reply	other threads:[~2012-08-10 16:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10  2:10 [Qemu-devel] [PATCH v8 0/7] file descriptor passing using fd sets Corey Bryant
2012-08-10  2:10 ` [Qemu-devel] [PATCH v8 1/7] qemu-char: Add MSG_CMSG_CLOEXEC flag to recvmsg Corey Bryant
2012-08-10  2:10 ` [Qemu-devel] [PATCH v8 2/7] qapi: Introduce add-fd, remove-fd, query-fdsets Corey Bryant
2012-08-10  5:57   ` Eric Blake
2012-08-10 13:01     ` Corey Bryant
2012-08-10  7:20   ` Stefan Hajnoczi
2012-08-10 14:21     ` Corey Bryant
2012-08-10 16:08   ` Kevin Wolf [this message]
2012-08-10 16:41     ` Corey Bryant
2012-08-10  2:10 ` [Qemu-devel] [PATCH v8 3/7] monitor: Clean up fd sets on monitor disconnect Corey Bryant
2012-08-10  2:10 ` [Qemu-devel] [PATCH v8 4/7] block: Prevent detection of /dev/fdset/ as floppy Corey Bryant
2012-08-10  2:10 ` [Qemu-devel] [PATCH v8 5/7] block: Convert open calls to qemu_open Corey Bryant
2012-08-10  2:10 ` [Qemu-devel] [PATCH v8 6/7] block: Convert close calls to qemu_close Corey Bryant
2012-08-10  2:10 ` [Qemu-devel] [PATCH v8 7/7] block: Enable qemu_open/close to work with fd sets Corey Bryant
2012-08-10  6:16   ` Eric Blake
2012-08-10 14:17     ` Corey Bryant
2012-08-10 15:25       ` Eric Blake
2012-08-10 15:44         ` Corey Bryant
2012-08-10 16:34   ` Kevin Wolf
2012-08-10 16:56     ` Corey Bryant
2012-08-10 17:03       ` Corey Bryant
2012-08-10 16:36 ` [Qemu-devel] [PATCH v8 0/7] file descriptor passing using " Kevin Wolf
2012-08-10 16:57   ` Corey Bryant

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=5025320C.40206@redhat.com \
    --to=kwolf@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=eblake@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    /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).