linux-kernel - Re: [PATCH] virtio: virtio 1.0 cs04 spec compliance for reset

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <570328C1.9010709@redhat.com>
Date:	Tue, 5 Apr 2016 10:53:53 +0800
From:	Jason Wang <jasowang@...hat.com>
To:	"Michael S. Tsirkin" <mst@...hat.com>, linux-kernel@...r.kernel.org
Cc:	stable@...r.kernel.org, virtualization@...ts.linux-foundation.org,
	Bandan Das <bsd@...hat.com>
Subject: Re: [PATCH] virtio: virtio 1.0 cs04 spec compliance for reset



On 04/03/2016 08:26 PM, Michael S. Tsirkin wrote:
> The spec says: after writing 0 to device_status, the driver MUST wait
> for a read of device_status to return 0 before reinitializing the
> device.
>
> Cc: stable@...r.kernel.org
> Signed-off-by: Michael S. Tsirkin <mst@...hat.com>
> ---
>  drivers/virtio/virtio_pci_modern.c | 11 ++++++++---
>  1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/virtio/virtio_pci_modern.c b/drivers/virtio/virtio_pci_modern.c
> index f6f28cc..e76bd91 100644
> --- a/drivers/virtio/virtio_pci_modern.c
> +++ b/drivers/virtio/virtio_pci_modern.c
> @@ -17,6 +17,7 @@
>   *
>   */
>  
> +#include <linux/delay.h>
>  #define VIRTIO_PCI_NO_LEGACY
>  #include "virtio_pci_common.h"
>  
> @@ -271,9 +272,13 @@ static void vp_reset(struct virtio_device *vdev)
>  	struct virtio_pci_device *vp_dev = to_vp_device(vdev);
>  	/* 0 status means a reset. */
>  	vp_iowrite8(0, &vp_dev->common->device_status);
> -	/* Flush out the status write, and flush in device writes,
> -	 * including MSI-X interrupts, if any. */
> -	vp_ioread8(&vp_dev->common->device_status);
> +	/* After writing 0 to device_status, the driver MUST wait for a read of
> +	 * device_status to return 0 before reinitializing the device.
> +	 * This will flush out the status write, and flush in device writes,
> +	 * including MSI-X interrupts, if any.
> +	 */
> +	while (vp_ioread8(&vp_dev->common->device_status))
> +		msleep(1);
>  	/* Flush pending VQ/configuration callbacks. */
>  	vp_synchronize_vectors(vdev);
>  }

Acked-by: Jason Wang <jasowang@...hat.com>