Akihiko Odaki 15377f6e79 msix: Assert that specified vector is in range ... There were several different ways to deal with the situation where the vector specified for a msix function is out of bound: - early return a function and keep progresssing - propagate the error to the caller - mark msix unusable - assert it is in bound - just ignore An out-of-bound vector should not be specified if the device implementation is correct so let msix functions always assert that the specified vector is in range. An exceptional case is virtio-pci, which allows the guest to configure vectors. For virtio-pci, it is more appropriate to introduce its own checks because it is sometimes too late to check the vector range in msix functions. Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com> Message-Id: <20220829083524.143640-1-akihiko.odaki@daynix.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Reviewed-by: Yuval Shaia <yuval.shaia.ml@gmail.com> Signed-off-by: Akihiko Odaki &lt;<a href="mailto:akihiko.odaki@daynix.com" target="_blank">akihiko.odaki@daynix.com</a>&gt;<br>		2022-11-07 14:08:17 -05:00
..
pvrdma_cmd.c	hw/rdma: Fix possible mremap overflow in the pvrdma device (CVE-2021-3582)	2021-07-04 22:47:51 +03:00
pvrdma_dev_ring.c	Use g_new() & friends where that makes obvious sense	2022-03-21 15:44:44 +01:00
pvrdma_dev_ring.h	pvrdma: wean code off pvrdma_ring.h kernel header	2021-03-15 16:41:22 +08:00
pvrdma_main.c	msix: Assert that specified vector is in range	2022-11-07 14:08:17 -05:00
pvrdma_qp_ops.c	Use g_new() & friends where that makes obvious sense	2022-03-21 15:44:44 +01:00
pvrdma_qp_ops.h	Clean up header guards that don't match their file name	2019-05-13 08:58:55 +02:00
pvrdma.h	pvrdma: wean code off pvrdma_ring.h kernel header	2021-03-15 16:41:22 +08:00
trace-events	docs: fix references to docs/devel/tracing.rst	2021-06-02 06:51:09 +02:00
trace.h	trace: switch position of headers to what Meson requires	2020-08-21 06:18:24 -04:00