On Mon, Feb 01, 2021 at 02:06:53PM +0100, Eugenio Perez Martin wrote:
On Mon, Feb 1, 2021 at 1:00 PM Stefano Garzarella wrote:
On Fri, Jan 29, 2021 at 10:07:28AM +0100, Eugenio Pérez wrote:
>Not checking this can lead to invalid dev->vdev member access in
>vhost_device_iotlb_miss if backend is
On Mon, Feb 1, 2021 at 1:00 PM Stefano Garzarella wrote:
>
> On Fri, Jan 29, 2021 at 10:07:28AM +0100, Eugenio Pérez wrote:
> >Not checking this can lead to invalid dev->vdev member access in
> >vhost_device_iotlb_miss if backend issue an iotlb message in a bad
> >timing, either maliciously or by
On Fri, Jan 29, 2021 at 10:07:28AM +0100, Eugenio Pérez wrote:
Not checking this can lead to invalid dev->vdev member access in
vhost_device_iotlb_miss if backend issue an iotlb message in a bad
timing, either maliciously or by a bug.
Reproduced rebooting a guest with testpmd in txonly forward m
On 2021/1/29 下午5:07, Eugenio Pérez wrote:
Not checking this can lead to invalid dev->vdev member access in
vhost_device_iotlb_miss if backend issue an iotlb message in a bad
timing, either maliciously or by a bug.
Reproduced rebooting a guest with testpmd in txonly forward mode.
#0 0x55
Version 2 of ("vhost-user: Check for iotlb callback in iotlb_miss") [1].
Starting a new series, since the title does not reflect the changes anymore.
Thanks!
[1] https://patchew.org/QEMU/20210127204449.745365-1-epere...@redhat.com/
On Fri, Jan 29, 2021 at 10:08 AM Eugenio Pérez wrote:
>
> Not
Not checking this can lead to invalid dev->vdev member access in
vhost_device_iotlb_miss if backend issue an iotlb message in a bad
timing, either maliciously or by a bug.
Reproduced rebooting a guest with testpmd in txonly forward mode.
#0 0x55994394 in vhost_device_iotlb_miss (
de
