Michael S. Tsirkin d96f66edf7 virtio_pci: fix virtio spec compliance on restore ...

commit 6fbc198cf6 upstream.

On restore, virtio pci does the following:
+ set features
+ init vqs etc - device can be used at this point!
+ set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits

This is in violation of the virtio spec, which
requires the following order:
- ACKNOWLEDGE
- DRIVER
- init vqs
- DRIVER_OK

This behaviour will break with hypervisors that assume spec compliant
behaviour.  It seems like a good idea to have this patch applied to
stable branches to reduce the support butden for the hypervisors.

Cc: Amit Shah <amit.shah@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

2014-11-14 08:47:55 -08:00

..

config.c

Remove all #inclusions of asm/system.h

2012-03-28 18:30:03 +01:00

Kconfig

drivers/virtio: remove depends on CONFIG_EXPERIMENTAL

2013-01-11 11:39:04 -08:00

Makefile

virtio: remove CONFIG_VIRTIO_RING

2012-09-28 15:05:15 +09:30

virtio_balloon.c

virtio_balloon: don't softlockup on huge balloon changes.

2014-05-13 13:59:41 +02:00

virtio_mmio.c

virtio: make config_ops const

2013-02-11 15:32:17 +10:30

virtio_pci.c

virtio_pci: fix virtio spec compliance on restore

2014-11-14 08:47:55 -08:00

virtio_ring.c

virtio: support unlocked queue poll

2013-07-28 16:29:55 -07:00

virtio.c

Merge tag 'virtio-next-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux

2012-12-20 08:37:05 -08:00