From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH V2 1/3] virtio: guard against NULL pfn
Date: Mon, 13 Mar 2017 10:55:15 +0100 [thread overview]
Message-ID: <20170313105515.75981fb9.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1489386583-11564-1-git-send-email-jasowang@redhat.com>
On Mon, 13 Mar 2017 14:29:41 +0800
Jason Wang <jasowang@redhat.com> wrote:
> To avoid access stale memory region cache after reset, this patch
> check the existence of virtqueue pfn for all exported virtqueue access
> helpers before trying to use them.
>
> Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> hw/virtio/virtio.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
> index efce4b3..76cc81b 100644
> --- a/hw/virtio/virtio.c
> +++ b/hw/virtio/virtio.c
> @@ -322,6 +322,10 @@ static int virtio_queue_empty_rcu(VirtQueue *vq)
> return 0;
> }
>
> + if (unlikely(!vq->vring.avail)) {
> + return 0;
Shouldn't that rather return !0 (denoting a non-existing queue as
empty)?
> + }
> +
> return vring_avail_idx(vq) == vq->last_avail_idx;
> }
>
> @@ -333,6 +337,10 @@ int virtio_queue_empty(VirtQueue *vq)
> return 0;
> }
>
> + if (unlikely(!vq->vring.avail)) {
> + return 0;
Likewise.
> + }
> +
> rcu_read_lock();
> empty = vring_avail_idx(vq) == vq->last_avail_idx;
> rcu_read_unlock();
> @@ -431,6 +439,10 @@ void virtqueue_fill(VirtQueue *vq, const VirtQueueElement *elem,
> return;
> }
>
> + if (unlikely(!vq->vring.used)) {
> + return;
> + }
> +
> idx = (idx + vq->used_idx) % vq->vring.num;
>
> uelem.id = elem->index;
> @@ -448,6 +460,10 @@ void virtqueue_flush(VirtQueue *vq, unsigned int count)
> return;
> }
>
> + if (unlikely(!vq->vring.used)) {
> + return;
> + }
> +
> /* Make sure buffer is written before we update index. */
> smp_wmb();
> trace_virtqueue_flush(vq, count);
> @@ -546,6 +562,11 @@ void virtqueue_get_avail_bytes(VirtQueue *vq, unsigned int *in_bytes,
> int64_t len = 0;
> int rc;
>
> + if (unlikely(!vq->vring.desc)) {
> + *in_bytes = *out_bytes = 0;
I think you need to check for in_bytes and out_bytes being !NULL first.
> + return;
> + }
> +
> rcu_read_lock();
> idx = vq->last_avail_idx;
> total_bufs = in_total = out_total = 0;
next prev parent reply other threads:[~2017-03-13 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 6:29 [Qemu-devel] [PATCH V2 1/3] virtio: guard against NULL pfn Jason Wang
2017-03-13 6:29 ` [Qemu-devel] [PATCH V2 2/3] virtio: destroy region cache during reset Jason Wang
2017-03-13 10:05 ` Cornelia Huck
2017-03-13 10:20 ` Paolo Bonzini
2017-03-14 2:14 ` Jason Wang
2017-03-14 2:13 ` Jason Wang
2017-03-13 6:29 ` [Qemu-devel] [PATCH V2 3/3] virtio: validate address space cache during init Jason Wang
2017-03-13 10:15 ` Cornelia Huck
2017-03-13 9:55 ` Cornelia Huck [this message]
2017-03-13 10:18 ` [Qemu-devel] [PATCH V2 1/3] virtio: guard against NULL pfn Paolo Bonzini
2017-03-14 2:37 ` Jason Wang
2017-03-14 2:02 ` Jason Wang
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=20170313105515.75981fb9.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).