From: Cornelia Huck <cohuck@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
zhangboxian <zhangboxian@huawei.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v1 1/2] virtio: check VirtQueue Vring object is set
Date: Fri, 24 Nov 2017 10:01:14 +0100 [thread overview]
Message-ID: <20171124100114.1d295940.cohuck@redhat.com> (raw)
In-Reply-To: <20171124075542.16979-2-ppandit@redhat.com>
On Fri, 24 Nov 2017 13:25:41 +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
> 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 | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> Updated: add vring.num check to virtio_queue_update_rings
> -> https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg04499.html
>
> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> index 5884ce3480..0940f1daf3 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 */
The check now implies "not yet setup or non-existing queue", no?
(Not that the check is wrong.)
> 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);
> }
> @@ -1494,8 +1497,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)
I think you also need to check for num in virtio_queue_set_rings().
next prev parent reply other threads:[~2017-11-24 9:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 7:55 [Qemu-devel] [PATCH v1 0/2] check VirtiQueue Vring objects P J P
2017-11-24 7:55 ` [Qemu-devel] [PATCH v1 1/2] virtio: check VirtQueue Vring object is set P J P
2017-11-24 9:01 ` Cornelia Huck [this message]
2017-11-24 11:54 ` Stefan Hajnoczi
2017-11-24 7:55 ` [Qemu-devel] [PATCH v1 2/2] tests: add test to check VirtQueue object P J P
2017-11-24 11:49 ` Stefan Hajnoczi
2017-11-24 9:42 ` [Qemu-devel] [PATCH v1 0/2] check VirtiQueue Vring objects Paolo Bonzini
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=20171124100114.1d295940.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).