diff options
| author | Stefan Hajnoczi | 2016-09-07 17:51:25 +0200 |
|---|---|---|
| committer | Michael S. Tsirkin | 2016-09-09 19:58:34 +0200 |
| commit | 4b7f91ed0270a371e1933efa21ba600b6da23ab9 (patch) | |
| tree | 54ccffe98df3b408feaa06f52abeced00c6b4e2a /scripts/switch-timer-api | |
| parent | virtio-pci: reduce modern_mem_bar size (diff) | |
| download | qemu-4b7f91ed0270a371e1933efa21ba600b6da23ab9.tar.gz qemu-4b7f91ed0270a371e1933efa21ba600b6da23ab9.tar.xz qemu-4b7f91ed0270a371e1933efa21ba600b6da23ab9.zip | |
virtio: zero vq->inuse in virtio_reset()
vq->inuse must be zeroed upon device reset like most other virtqueue
fields.
In theory, virtio_reset() just needs assert(vq->inuse == 0) since
devices must clean up in-flight requests during reset (requests cannot
not be leaked!).
In practice, it is difficult to achieve vq->inuse == 0 across reset
because balloon, blk, 9p, etc implement various different strategies for
cleaning up requests. Most devices call g_free(elem) directly without
telling virtio.c that the VirtQueueElement is cleaned up. Therefore
vq->inuse is not decremented during reset.
This patch zeroes vq->inuse and trusts that devices are not leaking
VirtQueueElements across reset.
I will send a follow-up series that refactors request life-cycle across
all devices and converts vq->inuse = 0 into assert(vq->inuse == 0) but
this more invasive approach is not appropriate for stable trees.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-stable <qemu-stable@nongnu.org>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Ladi Prosek <lprosek@redhat.com>
Diffstat (limited to 'scripts/switch-timer-api')
0 files changed, 0 insertions, 0 deletions
