Eric Auger ca50ec377c vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE ... Commit e2ae38cf3d ("vhost: fix hung thread due to erroneous iotlb entries") Forbade vhost iotlb msg with null size to prevent entries with size = start = 0 and last = ULONG_MAX to end up in the iotlb. Then commit 95932ab2ea ("vhost: allow batching hint without size") only applied the check for VHOST_IOTLB_UPDATE and VHOST_IOTLB_INVALIDATE message types to fix a regression observed with batching hit. Still, the introduction of that check introduced a regression for some users attempting to invalidate the whole ULONG_MAX range by setting the size to 0. This is the case with qemu/smmuv3/vhost integration which does not work anymore. It Looks safe to partially revert the original commit and allow VHOST_IOTLB_INVALIDATE messages with null size. vhost_iotlb_del_range() will compute a correct end iova. Same for vhost_vdpa_iotlb_unmap(). Signed-off-by: Eric Auger <eric.auger@redhat.com> Fixes: e2ae38cf3d ("vhost: fix hung thread due to erroneous iotlb entries") Cc: stable@vger.kernel.org # v5.17+ Acked-by: Jason Wang <jasowang@redhat.com> Message-Id: <20230927140544.205088-1-eric.auger@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>		2023-10-18 11:29:56 -04:00
..
iotlb.c
Kconfig
Makefile
net.c	vhost: convert poll work to be vq based	2023-07-03 12:15:13 -04:00
scsi.c	vhost-scsi: Rename vhost_scsi_iov_to_sgl	2023-08-10 15:24:28 -04:00
test.c
test.h
vdpa.c	vdpa: add get_backend_features vdpa operation	2023-09-03 18:10:22 -04:00
vhost.c	vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE	2023-10-18 11:29:56 -04:00
vhost.h	vhost: Make parameter name match of vhost_get_vq_desc()	2023-07-03 12:15:15 -04:00
vringh.c	vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()	2023-10-04 08:26:48 +01:00
vsock.c	vhost_sock: convert to vhost_vq_work_queue	2023-07-03 12:15:13 -04:00