From: Jason Wang <jasowang@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2 2/3] virtio: destroy region cache during reset
Date: Tue, 14 Mar 2017 10:13:37 +0800 [thread overview]
Message-ID: <0c1a620f-90e2-1f2b-8615-ed17b88b1272@redhat.com> (raw)
In-Reply-To: <20170313110523.549e4a99.cornelia.huck@de.ibm.com>
On 2017年03月13日 18:05, Cornelia Huck wrote:
> On Mon, 13 Mar 2017 14:29:42 +0800
> Jason Wang <jasowang@redhat.com> wrote:
>
>> We don't destroy region cache during reset which can make the maps
>> of previous driver leaked to a buggy or malicious driver that don't
>> set vring address before starting to use the device. Fix this by
>> destroy the region cache during reset and validate it before trying to
>> see them.
>>
>> Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> Changes from v1:
>> - switch to use rcu in virtio_virtqueue_region_cache()
>> - use unlikely() when needed
>> ---
>> hw/virtio/virtio.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++-------
>> 1 file changed, 53 insertions(+), 7 deletions(-)
>>
>> diff --git a/hw/virtio/virtio.c b/hw/virtio/virtio.c
>> index 76cc81b..f086452 100644
>> --- a/hw/virtio/virtio.c
>> +++ b/hw/virtio/virtio.c
>> @@ -190,6 +190,10 @@ static inline uint16_t vring_avail_flags(VirtQueue *vq)
>> {
>> VRingMemoryRegionCaches *caches = atomic_rcu_read(&vq->vring.caches);
>> hwaddr pa = offsetof(VRingAvail, flags);
>> + if (unlikely(!caches)) {
>> + virtio_error(vq->vdev, "Cannot map avail flags");
>> + return 0;
> I'm still not 100% convinced of those checks; but they don't do any
> harm.
Right, consider we've already had patch 1, I think it should be fine to
use assert here.
>
>> + }
>> return virtio_lduw_phys_cached(vq->vdev, &caches->avail, pa);
>> }
>>
> (...)
>
>> +static void virtio_virtqueue_reset_region_cache(struct VirtQueue *vq)
>> +{
>> + VRingMemoryRegionCaches *caches;
>> +
>> + caches = atomic_read(&vq->vring.caches);
>> + atomic_set(&vq->vring.caches, NULL);
> Needs atomic_rcu_set(), I think.
Any atomic write should be fine here, but I agree atomic_rcu_set() is
better. Will use it in next version.
Thanks
>
>> + if (caches) {
>> + call_rcu(caches, virtio_free_region_cache, rcu);
>> + }
>> +}
>> +
>> void virtio_reset(void *opaque)
>> {
>> VirtIODevice *vdev = opaque;
>
next prev parent reply other threads:[~2017-03-14 2:13 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 [this message]
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 ` [Qemu-devel] [PATCH V2 1/3] virtio: guard against NULL pfn Cornelia Huck
2017-03-13 10:18 ` 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=0c1a620f-90e2-1f2b-8615-ed17b88b1272@redhat.com \
--to=jasowang@redhat.com \
--cc=cornelia.huck@de.ibm.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).