From: Hanna Czenczek <hreitz@redhat.com>
To: German Maglione <gmaglione@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] virtio: Fix packed virtqueue used_idx mask
Date: Tue, 25 Jul 2023 17:21:44 +0200 [thread overview]
Message-ID: <2a4dd14f-4405-33f5-da68-ddf66a225cb7@redhat.com> (raw)
In-Reply-To: <CAJh=p+5sTOVPmSm-LeV1SJxTQW0dOuL_Lz2GTcdCK6MY6V7LxQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2893 bytes --]
On 25.07.23 16:04, German Maglione wrote:
>
>
> On Fri, Jul 21, 2023 at 3:51 PM Hanna Czenczek <hreitz@redhat.com> wrote:
>
> virtio_queue_packed_set_last_avail_idx() is used by vhost devices
> to set
> the internal queue indices to what has been reported by the vhost
> back-end through GET_VRING_BASE. For packed virtqueues, this
> 32-bit value is expected to contain both the device's internal
> avail and
> used indices, as well as their respective wrap counters.
>
> To get the used index, we shift the 32-bit value right by 16, and then
> apply a mask of 0x7ffff. That seems to be a typo, because it
> should be
> 0x7fff; first of all, the virtio specification says that the maximum
> queue size for packed virt queues is 2^15, so the indices cannot
> exceed
> 2^15 - 1 anyway, making 0x7fff the correct mask. Second, the mask
> clearly is wrong from context, too, given that (A) `idx & 0x70000`
> must
> be 0 at this point (`idx` is 32 bit and was shifted to the right by 16
> already), (B) `idx & 0x8000` is the used_wrap_counter, so should
> not be
> part of the used index, and (C) `vq->used_idx` is a `uint16_t`, so
> cannot fit the 0x70000 part of the mask anyway.
>
> This most likely never produced any guest-visible bugs, though,
> because
> for a vhost device, qemu will probably not evaluate the used index
> outside of virtio_queue_packed_get_last_avail_idx(), where we
> reconstruct the 32-bit value from avail and used indices and their
> wrap
> counters again. There, it does not matter whether the highest bit of
> the used_idx is the used index wrap counter, because we put the wrap
> counter exactly in that position anyway.
>
> Signed-off-by: Hanna Czenczek <hreitz@redhat.com>
> ---
> hw/virtio/virtio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> index 295a603e58..309038fd46 100644
> --- a/hw/virtio/virtio.c
> +++ b/hw/virtio/virtio.c
> @@ -3321,7 +3321,7 @@ static void
> virtio_queue_packed_set_last_avail_idx(VirtIODevice *vdev,
> vq->last_avail_wrap_counter =
> vq->shadow_avail_wrap_counter = !!(idx & 0x8000);
> idx >>= 16;
> - vq->used_idx = idx & 0x7ffff;
> + vq->used_idx = idx & 0x7fff;
>
>
> isn't there a macro with this value?
> or a macro that convert a number of bits in a mask?, something like:
> #define BIT_MASK(n) (~(~0 << n))
((1 << n) - 1) would be what I’d come up with; in any case, there is
MAKE_64BIT_MASK in qemu/bitops.h, but I don’t know whether I really like
MAKE_64BIT_MASK(0, 15) more than 0x7fff. In addition, that would need
to be done throughout that function and I don’t think that’s worth it
right now.
Hanna
[-- Attachment #2: Type: text/html, Size: 4770 bytes --]
next prev parent reply other threads:[~2023-07-25 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 13:49 [PATCH] virtio: Fix packed virtqueue used_idx mask Hanna Czenczek
2023-07-25 14:04 ` German Maglione
2023-07-25 15:21 ` Hanna Czenczek [this message]
2023-07-25 14:53 ` German Maglione
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=2a4dd14f-4405-33f5-da68-ddf66a225cb7@redhat.com \
--to=hreitz@redhat.com \
--cc=gmaglione@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).