Jason Wang 2d66f997f0 vhost: correctly check the iova range when waking virtqueue ... We don't wakeup the virtqueue if the first byte of pending iova range is the last byte of the range we just got updated. This will lead a virtqueue to wait for IOTLB updating forever. Fixing by correct the check and wake up the virtqueue in this case. Fixes: 6b1e6cc785 ("vhost: new device IOTLB API") Reported-by: Peter Xu <peterx@redhat.com> Signed-off-by: Jason Wang <jasowang@redhat.com> Reviewed-by: Peter Xu <peterx@redhat.com> Tested-by: Peter Xu <peterx@redhat.com> Acked-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>		2018-08-25 17:39:41 -07:00
..
Kconfig
Kconfig.vringh
Makefile
net.c	vhost: switch to use new message format	2018-08-06 10:41:04 -07:00
scsi.c	scsi: target: loop, usb, vhost, xen: use target_remove_session	2018-08-02 15:29:31 -04:00
test.c	treewide: kmalloc() -> kmalloc_array()	2018-06-12 16:19:22 -07:00
test.h
vhost.c	vhost: correctly check the iova range when waking virtqueue	2018-08-25 17:39:41 -07:00
vhost.h	vhost: switch to use new message format	2018-08-06 10:41:04 -07:00
vringh.c	treewide: kmalloc() -> kmalloc_array()	2018-06-12 16:19:22 -07:00
vsock.c	fw_cfg, vhost: features fixes	2018-04-06 19:21:41 -07:00