From: Cornelia Huck <cohuck@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
zhangboxian <zhangboxian@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v3 1/2] virtio: check VirtQueue Vring object is set
Date: Mon, 27 Nov 2017 11:03:34 +0100 [thread overview]
Message-ID: <20171127110334.2e5eb633.cohuck@redhat.com> (raw)
In-Reply-To: <20171124183446.7308-2-ppandit@redhat.com>
On Sat, 25 Nov 2017 00:04:45 +0530
P J P <ppandit@redhat.com> wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> An user could attempt to use an uninitialised VirtQueue object
s/An user/A guest/ ?
> or unset Vring.align leading to a arithmetic exception. Add check
> to avoid it.
>
> Reported-by: Zhangboxian <zhangboxian@huawei.com>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> ---
> hw/virtio/virtio.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> index 5884ce3480..c01eac87a5 100644
> --- a/hw/virtio/virtio.c
> +++ b/hw/virtio/virtio.c
> @@ -182,7 +182,7 @@ void virtio_queue_update_rings(VirtIODevice *vdev, int n)
> {
> VRing *vring = &vdev->vq[n].vring;
>
> - if (!vring->desc) {
> + if (!vdev->vq[n].vring.num || !vring->desc || !vring->align) {
> /* not yet setup -> nothing to do */
> return;
> }
> @@ -1414,6 +1414,9 @@ void virtio_config_modern_writel(VirtIODevice *vdev,
>
> void virtio_queue_set_addr(VirtIODevice *vdev, int n, hwaddr addr)
> {
> + if (!vdev->vq[n].vring.num) {
> + return;
> + }
> vdev->vq[n].vring.desc = addr;
> virtio_queue_update_rings(vdev, n);
> }
> @@ -1426,6 +1429,9 @@ hwaddr virtio_queue_get_addr(VirtIODevice *vdev, int n)
> void virtio_queue_set_rings(VirtIODevice *vdev, int n, hwaddr desc,
> hwaddr avail, hwaddr used)
> {
> + if (!vdev->vq[n].vring.num || !desc || !vdev->vq[n].vring.align) {
Checking for !desc is wrong (why shouldn't a driver be able to unset a
descriptor table?)
The check for align is not really needed, as virtio-1 disallows setting
align anyway.
> + return;
> + }
> vdev->vq[n].vring.desc = desc;
> vdev->vq[n].vring.avail = avail;
> vdev->vq[n].vring.used = used;
> @@ -1494,8 +1500,10 @@ void virtio_queue_set_align(VirtIODevice *vdev, int n, int align)
> */
> assert(k->has_variable_vring_alignment);
>
> - vdev->vq[n].vring.align = align;
> - virtio_queue_update_rings(vdev, n);
> + if (align) {
> + vdev->vq[n].vring.align = align;
> + virtio_queue_update_rings(vdev, n);
> + }
> }
>
> static bool virtio_queue_notify_aio_vq(VirtQueue *vq)
next prev parent reply other threads:[~2017-11-27 10:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 18:34 [Qemu-devel] [PATCH v3 0/2] check VirtiQueue Vring objects P J P
2017-11-24 18:34 ` [Qemu-devel] [PATCH v3 1/2] virtio: check VirtQueue Vring object is set P J P
2017-11-27 10:03 ` Cornelia Huck [this message]
2017-11-27 11:15 ` Stefan Hajnoczi
2017-11-27 17:55 ` P J P
2017-11-28 9:11 ` Cornelia Huck
2017-11-28 10:37 ` Stefan Hajnoczi
2017-11-28 11:27 ` P J P
2017-11-28 12:00 ` Cornelia Huck
2017-11-29 10:11 ` P J P
2017-11-29 11:16 ` Cornelia Huck
2017-11-30 9:16 ` P J P
2017-11-24 18:34 ` [Qemu-devel] [PATCH v3 2/2] tests: add test to check VirtQueue object P J P
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=20171127110334.2e5eb633.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=zhangboxian@huawei.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;
as well as URLs for NNTP newsgroup(s).