From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
Cc: svt-core@virtuozzo.com, den@openvz.org, andrey.drobyshev@virtuozzo.com
Subject: Re: [QEMU HCI-8.0 PATCH 3/5] vhost-blk: add read-only flag
Date: Thu, 03 Sep 2026 17:56:04 +0300 [thread overview]
Message-ID: <178844736480.581266.17142871141380337557.b4-review@b4> (raw)
In-Reply-To: <20260903123204.24035-4-andrey.zhadchenko@virtuozzo.com>
> and set RO respectively. Also compare BLKROGET with the selected
Nit: make commit message start with their own sentence.
> mode and reject r/w if needed.
>
> https://virtuozzo.atlassian.net/browse/VSTOR-143437
> Signed-off-by: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
>
> diff --git a/hw/block/vhost-blk.c b/hw/block/vhost-blk.c
> index a3e0010982f..47b6e560d47 100644
> --- a/hw/block/vhost-blk.c
> +++ b/hw/block/vhost-blk.c
> @@ -24,6 +24,7 @@
> #include "system/system.h"
> #include "linux-headers/linux/vhost.h"
> #include <sys/ioctl.h>
> +#include <linux/fs.h>
Previous patch removes the header, now we add it back. Let's just not
touch it.
> #include "system/runstate.h"
>
> static int vhost_blk_start(VirtIODevice *vdev)
> @@ -233,8 +234,10 @@ static bool vhost_blk_open_backend(VHostBlk *s, Error **errp)
> {
> BlockConf *conf = &s->conf.conf;
> struct stat st;
> + int readonly;
> + int open_flags = s->conf.readonly ? O_RDONLY : O_RDWR;
>
> - s->backend_fd = qemu_open(s->conf.devpath, O_RDWR, errp);
> + s->backend_fd = qemu_open(s->conf.devpath, open_flags, errp);
> if (s->backend_fd < 0) {
> error_prepend(errp, "vhost-blk: unable to open backend: ");
> return false;
> @@ -252,6 +255,19 @@ static bool vhost_blk_open_backend(VHostBlk *s, Error **errp)
> goto fail;
> }
>
> + if (ioctl(s->backend_fd, BLKROGET, &readonly) < 0) {
> + error_setg_errno(errp, errno,
> + "vhost-blk: unable to get read-only status of '%s'",
> + s->conf.devpath);
> + goto fail;
> + }
> +
> + if (readonly && !s->conf.readonly) {
> + error_setg(errp, "vhost-blk: '%s' is read-only",
> + s->conf.devpath);
> + goto fail;
> + }
> +
How about doing it similarly to file-posix:
if (!s->conf.readonly) {
if (ioctl(s->backend_fd, BLKROGET, &readonly) < 0) {
error_setg_errno(errp, errno,
"vhost-blk: unable to get read-only status of "
"'%s'", s->conf.devpath);
goto fail;
}
if (readonly) {
error_setg_errno(errp, EROFS, "The device is not writable");
goto fail;
}
}
In addition: conf.readonly value comes from libvirt. conf.devpath is
also provided by libvirt. Shouldn't we check BLKROGET early on and fail
in libvirt instead of waiting till here? I'd prefer having both checks.
Leave the check here, but fail early on in libvirt.
Andrey
--
Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
next prev parent reply other threads:[~2026-09-03 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 12:31 [QEMU HCI-8.0 PATCH 0/5] vhost-blk change backend setup Andrey Zhadchenko
2026-09-03 12:32 ` [QEMU HCI-8.0 PATCH 1/5] blk: factor out validation Andrey Zhadchenko
2026-09-03 14:56 ` Andrey Drobyshev
2026-09-03 12:32 ` [QEMU HCI-8.0 PATCH 2/5] vhost-blk: change backend setup Andrey Zhadchenko
2026-09-03 14:56 ` Andrey Drobyshev
2026-09-03 15:27 ` Andrey Zhadchenko
2026-09-03 15:34 ` Andrey Drobyshev
2026-09-03 12:32 ` [QEMU HCI-8.0 PATCH 3/5] vhost-blk: add read-only flag Andrey Zhadchenko
2026-09-03 14:56 ` Andrey Drobyshev [this message]
2026-09-03 12:32 ` [QEMU HCI-8.0 PATCH 4/5] vhost-blk: watch the device for resize events Andrey Zhadchenko
2026-09-03 14:56 ` Andrey Drobyshev
2026-09-03 15:30 ` Andrey Zhadchenko
2026-09-03 15:45 ` Andrey Drobyshev
2026-09-03 15:50 ` Andrey Zhadchenko
2026-09-03 12:32 ` [QEMU HCI-8.0 PATCH 5/5] vhost-blk: filter uevents in the kernel Andrey Zhadchenko
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=178844736480.581266.17142871141380337557.b4-review@b4 \
--to=andrey.drobyshev@virtuozzo.com \
--cc=andrey.zhadchenko@virtuozzo.com \
--cc=den@openvz.org \
--cc=svt-core@virtuozzo.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