From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: "Carlos López" <clopez@suse.de>,
qemu-devel@nongnu.org, "Halil Pasic" <pasic@linux.ibm.com>,
"Eric Farman" <farman@linux.ibm.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"David Hildenbrand" <david@redhat.com>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Thomas Huth" <thuth@redhat.com>,
"open list:virtio-ccw" <qemu-s390x@nongnu.org>
Subject: Re: [PATCH] virtio: refresh vring region cache after updating a virtqueue size
Date: Fri, 10 Mar 2023 06:29:33 -0500 [thread overview]
Message-ID: <20230310062925-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <875ybajjbx.fsf@redhat.com>
On Thu, Mar 09, 2023 at 11:43:46AM +0100, Cornelia Huck wrote:
> On Thu, Mar 02 2023, Carlos López <clopez@suse.de> wrote:
>
> > When a virtqueue size is changed by the guest via
> > virtio_queue_set_num(), its region cache is not automatically updated.
> > If the size was increased, this could lead to accessing the cache out
> > of bounds. For example, in vring_get_used_event():
> >
> > static inline uint16_t vring_get_used_event(VirtQueue *vq)
> > {
> > return vring_avail_ring(vq, vq->vring.num);
> > }
> >
> > static inline uint16_t vring_avail_ring(VirtQueue *vq, int i)
> > {
> > VRingMemoryRegionCaches *caches = vring_get_region_caches(vq);
> > hwaddr pa = offsetof(VRingAvail, ring[i]);
> >
> > if (!caches) {
> > return 0;
> > }
> >
> > return virtio_lduw_phys_cached(vq->vdev, &caches->avail, pa);
> > }
> >
> > vq->vring.num will be greater than caches->avail.len, which will
> > trigger a failed assertion down the call path of
> > virtio_lduw_phys_cached().
> >
> > Fix this by calling virtio_queue_update_rings() after
> > virtio_queue_set_num() if we are not already calling
> > virtio_queue_set_rings().
>
> Don't we instead need to call virtio_init_region_cache() to update the
> caches? virtio_queue_set_rings() will calculate avail and used from
> desc, which looks wrong for modern devices.
Carlos?
> >
> > Signed-off-by: Carlos López <clopez@suse.de>
> > ---
> > hw/s390x/virtio-ccw.c | 1 +
> > hw/virtio/virtio-mmio.c | 5 ++---
> > hw/virtio/virtio-pci.c | 1 +
> > 3 files changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/hw/s390x/virtio-ccw.c b/hw/s390x/virtio-ccw.c
> > index e33e5207ab..89891ac58a 100644
> > --- a/hw/s390x/virtio-ccw.c
> > +++ b/hw/s390x/virtio-ccw.c
> > @@ -237,6 +237,7 @@ static int virtio_ccw_set_vqs(SubchDev *sch, VqInfoBlock *info,
> > return -EINVAL;
> > }
> > virtio_queue_set_num(vdev, index, num);
> > + virtio_queue_update_rings(vdev, index);
>
> Note that this is the non-legacy path.
>
> > } else if (virtio_queue_get_num(vdev, index) > num) {
> > /* Fail if we don't have a big enough queue. */
> > return -EINVAL;
> > diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
> > index 23ba625eb6..c74822308f 100644
> > --- a/hw/virtio/virtio-mmio.c
> > +++ b/hw/virtio/virtio-mmio.c
> > @@ -350,10 +350,9 @@ static void virtio_mmio_write(void *opaque, hwaddr offset, uint64_t value,
> > case VIRTIO_MMIO_QUEUE_NUM:
> > trace_virtio_mmio_queue_write(value, VIRTQUEUE_MAX_SIZE);
> > virtio_queue_set_num(vdev, vdev->queue_sel, value);
> > + virtio_queue_update_rings(vdev, vdev->queue_sel);
> >
> > - if (proxy->legacy) {
> > - virtio_queue_update_rings(vdev, vdev->queue_sel);
> > - } else {
> > + if (!proxy->legacy) {
> > proxy->vqs[vdev->queue_sel].num = value;
> > }
> > break;
> > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > index 247325c193..a0a2f2c965 100644
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -1554,6 +1554,7 @@ static void virtio_pci_common_write(void *opaque, hwaddr addr,
> > proxy->vqs[vdev->queue_sel].num = val;
> > virtio_queue_set_num(vdev, vdev->queue_sel,
> > proxy->vqs[vdev->queue_sel].num);
> > + virtio_queue_update_rings(vdev, vdev->queue_sel);
> > break;
> > case VIRTIO_PCI_COMMON_Q_MSIX:
> > vector = virtio_queue_vector(vdev, vdev->queue_sel);
next prev parent reply other threads:[~2023-03-10 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 10:14 [PATCH] virtio: refresh vring region cache after updating a virtqueue size Carlos López
2023-03-06 11:36 ` Thomas Huth
2023-03-09 10:43 ` Cornelia Huck
2023-03-10 11:29 ` Michael S. Tsirkin [this message]
2023-03-13 10:19 ` Carlos López
2023-03-15 13:11 ` Cornelia Huck
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=20230310062925-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clopez@suse.de \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.