qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jonathon Jongsma <jjongsma@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-block@nongnu.org, Hanna Reitz <hreitz@redhat.com>
Subject: Re: [PATCH v3 1/1] block/blkio: use qemu_open() to support fd passing for virtio-blk
Date: Thu, 11 May 2023 11:03:22 -0500	[thread overview]
Message-ID: <1a89ee2e-2368-4051-f9ec-018641721484@redhat.com> (raw)
In-Reply-To: <20230511091527.46620-2-sgarzare@redhat.com>

On 5/11/23 4:15 AM, Stefano Garzarella wrote:
> The virtio-blk-vhost-vdpa driver in libblkio 1.3.0 supports the new
> 'fd' property. Let's expose this to the user, so the management layer
> can pass the file descriptor of an already opened vhost-vdpa character
> device. This is useful especially when the device can only be accessed
> with certain privileges.
> 
> If the libblkio virtio-blk driver supports fd passing, let's always
> use qemu_open() to open the `path`, so we can handle fd passing
> from the management layer through the "/dev/fdset/N" special path.
> 
> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
> ---
> 
> Notes:
>      v3:
>      - use qemu_open() on `path` to simplify libvirt code [Jonathon]


Thanks

The one drawback now is that it doesn't seem possible for libvirt to 
introspect whether or not qemu supports passing an fd to the driver or 
not. When I was writing my initial patch (before I realized that it was 
missing fd-passing), I just checked for the existence of the 
virtio-blk-vhost-vdpa device. But we actually need to know both that 
this device exists and supports fd passing. As far as I can tell, 
versions 7.2.0 and 8.0.0 include this device but won't accept fds.

Jonathon


> 
>   block/blkio.c | 53 ++++++++++++++++++++++++++++++++++++++++++---------
>   1 file changed, 44 insertions(+), 9 deletions(-)
> 
> diff --git a/block/blkio.c b/block/blkio.c
> index 0cdc99a729..6a6f20f923 100644
> --- a/block/blkio.c
> +++ b/block/blkio.c
> @@ -672,25 +672,60 @@ static int blkio_virtio_blk_common_open(BlockDriverState *bs,
>   {
>       const char *path = qdict_get_try_str(options, "path");
>       BDRVBlkioState *s = bs->opaque;
> -    int ret;
> +    bool fd_supported = false;
> +    int fd, ret;
>   
>       if (!path) {
>           error_setg(errp, "missing 'path' option");
>           return -EINVAL;
>       }
>   
> -    ret = blkio_set_str(s->blkio, "path", path);
> -    qdict_del(options, "path");
> -    if (ret < 0) {
> -        error_setg_errno(errp, -ret, "failed to set path: %s",
> -                         blkio_get_error_msg());
> -        return ret;
> -    }
> -
>       if (!(flags & BDRV_O_NOCACHE)) {
>           error_setg(errp, "cache.direct=off is not supported");
>           return -EINVAL;
>       }
> +
> +    if (blkio_get_int(s->blkio, "fd", &fd) == 0) {
> +        fd_supported = true;
> +    }
> +
> +    /*
> +     * If the libblkio driver supports fd passing, let's always use qemu_open()
> +     * to open the `path`, so we can handle fd passing from the management
> +     * layer through the "/dev/fdset/N" special path.
> +     */
> +    if (fd_supported) {
> +        int open_flags;
> +
> +        if (flags & BDRV_O_RDWR) {
> +            open_flags = O_RDWR;
> +        } else {
> +            open_flags = O_RDONLY;
> +        }
> +
> +        fd = qemu_open(path, open_flags, errp);
> +        if (fd < 0) {
> +            return -EINVAL;
> +        }
> +
> +        ret = blkio_set_int(s->blkio, "fd", fd);
> +        if (ret < 0) {
> +            error_setg_errno(errp, -ret, "failed to set fd: %s",
> +                             blkio_get_error_msg());
> +            qemu_close(fd);
> +            return ret;
> +        }
> +    } else {
> +        ret = blkio_set_str(s->blkio, "path", path);
> +        if (ret < 0) {
> +            error_setg_errno(errp, -ret, "failed to set path: %s",
> +                             blkio_get_error_msg());
> +            return ret;
> +        }
> +    }
> +
> +    qdict_del(options, "path");
> +
>       return 0;
>   }
>   



  reply	other threads:[~2023-05-11 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  9:15 [PATCH v3 0/1] block/blkio: support 'fd' option for virtio-blk-vhost-vdpa driver Stefano Garzarella
2023-05-11  9:15 ` [PATCH v3 1/1] block/blkio: use qemu_open() to support fd passing for virtio-blk Stefano Garzarella
2023-05-11 16:03   ` Jonathon Jongsma [this message]
2023-05-15 10:10     ` Stefano Garzarella
2023-05-16 16:04       ` Jonathon Jongsma
2023-05-17  7:19         ` Stefano Garzarella
2023-05-17 14:30           ` Stefan Hajnoczi
2023-05-24  9:05             ` Stefano Garzarella
2023-05-24 19:16               ` Stefan Hajnoczi
2023-05-25 18:30             ` Markus Armbruster
2023-05-25 18:59               ` Jonathon Jongsma
2023-05-26 14:25               ` Stefano Garzarella

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=1a89ee2e-2368-4051-f9ec-018641721484@redhat.com \
    --to=jjongsma@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.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).