Eric Auger 3a6cee2bfb vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE ... commit ca50ec377c upstream. 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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2023-11-08 17:26:36 +01:00
..
Kconfig	…
Makefile	…
iotlb.c	vhost: handle error while adding split ranges to iotlb	2022-04-08 14:24:12 +02:00
net.c	vhost_net: revert upend_idx only on retriable error	2023-06-28 10:29:53 +02:00
scsi.c	…
test.c	…
test.h	…
vdpa.c	vhost_vdpa: support PACKED when setting-getting vring_base	2023-06-14 11:13:09 +02:00
vhost.c	vhost: Allow null msg.size on VHOST_IOTLB_INVALIDATE	2023-11-08 17:26:36 +01:00
vhost.h	vhost: support PACKED when setting-getting vring_base	2023-06-14 11:13:09 +02:00
vringh.c	vringh: don't use vringh_kiov_advance() in vringh_iov_xfer()	2023-10-10 21:59:05 +02:00
vsock.c	vhost/vsock: Fix error handling in vhost_vsock_init()	2023-01-12 11:59:11 +01:00