From: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
To: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1] drivers/vhost/blk: reject a head that is still in flight
Date: Thu, 29 Oct 2026 12:03:35 +0100 [thread overview]
Message-ID: <86fbc89a-f264-46f5-a008-fa096ad56f61@virtuozzo.com> (raw)
In-Reply-To: <20261028081459.3050162-1-alexander.ivanov@virtuozzo.com>
LGTM
Reviewed-by: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
On 10/28/26 09:14, Alexander Ivanov wrote:
> vhost_blk_req_handle() takes the request slot by head and overwrites it
> without checking that it is free. A guest that puts a head into the
> avail ring again while its request is in flight makes the slot get
> submitted twice: req_inflight is raised for each submission, but the
> completion path sees one slot and calls forget_request() once.
> req_inflight never drops to zero, and vhost_blk_flush() on backend drop
> leaves QEMU in D state forever with the block device pinned. The second
> submission also overwrites bio[], bio_nr and the iovecs of bios that
> are still in flight.
>
> Mark a slot in flight from bio submission until its completion is
> handled, both under vq->mutex, and fail the request if the guest posts
> an in-flight head. The caller reports the error on the vq error eventfd
> and stops processing the ring. Allocate the slots zeroed so the flag
> starts clear.
>
> https://virtuozzo.atlassian.net/browse/VSTOR-152123
> Fixes: d8722ff88c5d ("drivers/vhost: vhost-blk accelerator for virtio-blk guests")
> Feature: vhost-blk: in-kernel accelerator for virtio-blk guests
>
> Signed-off-by: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
> ---
> drivers/vhost/blk.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vhost/blk.c b/drivers/vhost/blk.c
> index b170439a1806..668986449373 100644
> --- a/drivers/vhost/blk.c
> +++ b/drivers/vhost/blk.c
> @@ -79,6 +79,7 @@ struct vhost_blk_req {
> u16 head;
> size_t len;
> int bio_err;
> + bool inflight;
>
> struct vhost_blk *blk;
> struct vhost_blk_vq *blk_vq;
> @@ -434,6 +435,7 @@ static int vhost_blk_req_submit(struct vhost_blk_req *req)
> if (ret < 0)
> goto out;
>
> + req->inflight = true;
> vhost_blk_bio_send(req);
> return ret;
>
> @@ -457,6 +459,9 @@ static int vhost_blk_req_handle(struct vhost_virtqueue *vq,
> u8 status;
>
> req = &blk_vq->req[head];
> + if (unlikely(req->inflight))
> + return -EBUSY;
> +
> req->blk_vq = blk_vq;
> req->head = head;
> req->blk = blk;
> @@ -628,6 +633,7 @@ static void vhost_blk_handle_host_kick(struct vhost_work *work)
> added = true;
> }
>
> + req->inflight = false;
> forget_request(req);
> }
>
> @@ -703,8 +709,8 @@ static int vhost_blk_setup_vqs(struct vhost_blk *blk)
> if (!vhost_vq_is_setup(vq))
> continue;
>
> - blk->vqs[i].req = kvmalloc_array(vq->num, sizeof(struct vhost_blk_req),
> - GFP_KERNEL);
> + blk->vqs[i].req = kvcalloc(vq->num, sizeof(struct vhost_blk_req),
> + GFP_KERNEL);
> if (!blk->vqs[i].req)
> return -ENOMEM;
>
_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2026-10-29 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 8:14 Alexander Ivanov
2026-10-29 11:03 ` Andrey Zhadchenko [this message]
2026-10-29 12:05 ` Konstantin Khorenko
2026-10-29 13:43 ` Alexander Ivanov
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=86fbc89a-f264-46f5-a008-fa096ad56f61@virtuozzo.com \
--to=andrey.zhadchenko@virtuozzo.com \
--cc=alexander.ivanov@virtuozzo.com \
--cc=devel@openvz.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