From: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
Subject: Re: [Devel] [PATCH VZ10 v3 5/5] drivers/vhost/blk: rework queue/backend setup
Date: Tue, 25 Aug 2026 15:27:52 +0200 [thread overview]
Message-ID: <cdd14089-2655-4d70-959b-9d96978cb3a6@virtuozzo.com> (raw)
In-Reply-To: <a248d20f-0af1-4f05-aa89-d696d5cf364c@virtuozzo.com>
On 8/25/26 15:22, Konstantin Khorenko wrote:
> On 8/25/26 14:51, Andrey Zhadchenko wrote:
>> vhost_blk_setup() is pretty bad: silently refusing changed vq->num
>> if requests are already allocated, fetching user input second time
>> (double-fetch vulnerability).
>> To handle this, tie request allocation to backend existence. After
>> all, if there is no backend, there is no point in having requests.
>> Also expand it to get rid of boilerplate drop_backend, flush,
>> fput sequence in a few places.
>>
>> https://virtuozzo.atlassian.net/browse/VSTOR-138640
>> Signed-off-by: Andrey Zhadchenko <andrey.zhadchenko@virtuozzo.com>
>> ---
> ...
>
>> +static int vhost_blk_setup_vqs(struct vhost_blk *blk)
>> +{
>> + struct vhost_virtqueue *vq;
>> + int i;
>> +
>> + for (i = 0; i < VHOST_BLK_VQ_MAX; i++) {
>> + vq = &blk->vqs[i].vq;
>> +
>> + if (!vhost_vq_is_setup(vq))
>> + continue;
>> +
>> + blk->vqs[i].req = kvmalloc_array(vq->num, sizeof(struct vhost_blk_req),
>> + GFP_KERNEL);
>> + if (!blk->vqs[i].req)
>> + return -ENOMEM;
>> +
>> + mutex_lock(&vq->mutex);
>> + vhost_vq_set_backend(vq, blk->backend);
>> + if (vhost_vq_init_access(vq)) {
>> + mutex_unlock(&vq->mutex);
>> + return -EFAULT;
>> + }
>> + mutex_unlock(&vq->mutex);
>
> Well, i agree that currently vhost_vq_init_access() can return -EFAULT only as an error,
> but may be it's still worth to write a more generic return ret code?
LGTM.
Original code was using this aprroach too, no idea why have I changed that.
Can you apply this in-place or do you want me to re-spin the series?
>
> int ret, i;
>
> for (i = 0; i < VHOST_BLK_VQ_MAX; i++) {
> ...
> mutex_lock(&vq->mutex);
> vhost_vq_set_backend(vq, blk->backend);
> ret = vhost_vq_init_access(vq);
> mutex_unlock(&vq->mutex);
> if (ret)
> return ret;
>
>
>
>> + }
>> +
>> + return 0;
>> }
>> ...
next prev parent reply other threads:[~2026-08-25 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 12:51 [Devel] [PATCH VZ10 v3 0/5] vhost-blk: fix protocol handling and backend setup Andrey Zhadchenko
2026-08-25 12:51 ` [Devel] [PATCH VZ10 v3 1/5] drivers/vhost/blk: harden get_id command Andrey Zhadchenko
2026-08-25 13:56 ` [Devel] [PATCH RHEL10 COMMIT] " Konstantin Khorenko
2026-08-25 12:51 ` [Devel] [PATCH VZ10 v3 2/5] drivers/vhost/blk: report correct used-ring lengths Andrey Zhadchenko
2026-08-25 13:56 ` [Devel] [PATCH RHEL10 COMMIT] " Konstantin Khorenko
2026-08-25 12:51 ` [Devel] [PATCH VZ10 v3 3/5] drivers/vhost/blk: fix flush support Andrey Zhadchenko
2026-08-25 13:56 ` [Devel] [PATCH RHEL10 COMMIT] " Konstantin Khorenko
2026-08-25 12:51 ` [Devel] [PATCH VZ10 v3 4/5] drivers/vhost/blk: fix sector alignment calculation Andrey Zhadchenko
2026-08-25 13:56 ` [Devel] [PATCH RHEL10 COMMIT] " Konstantin Khorenko
2026-08-25 12:51 ` [Devel] [PATCH VZ10 v3 5/5] drivers/vhost/blk: rework queue/backend setup Andrey Zhadchenko
2026-08-25 13:22 ` Konstantin Khorenko
2026-08-25 13:27 ` Andrey Zhadchenko [this message]
2026-08-25 13:42 ` Konstantin Khorenko
2026-08-25 13:57 ` [Devel] [PATCH RHEL10 COMMIT] " Konstantin Khorenko
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=cdd14089-2655-4d70-959b-9d96978cb3a6@virtuozzo.com \
--to=andrey.zhadchenko@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