Marc-André Lureau c4843a45e3 vhost-user: check vhost_user_{read,write}() return value ... The vhost-user code is quite inconsistent with error handling. Instead of ignoring some return values of read/write and silently going on with invalid state (invalid read for example), break the code flow when the error happened. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>		2016-07-29 00:33:48 +03:00
..
Makefile.objs	vring: remove	2016-02-25 13:14:19 +02:00
trace-events	trace: split out trace events for hw/virtio/ directory	2016-06-20 17:22:15 +01:00
vhost-backend.c	Use #include "..." for our own headers, <...> for others	2016-07-12 16:19:16 +02:00
vhost-user.c	vhost-user: check vhost_user_{read,write}() return value	2016-07-29 00:33:48 +03:00
vhost.c	vhost: use error_report() instead of fprintf(stderr,...)	2016-07-29 00:33:47 +03:00
virtio-balloon.c	virtio-balloon: Wrap in vmstate	2016-07-21 20:44:20 +03:00
virtio-bus.c	virtio: revert host notifiers to old semantics	2016-07-04 14:52:10 +03:00
virtio-mmio.c	virtio-mmio: format transport base address in BusClass.get_dev_path	2016-07-14 16:51:36 +01:00
virtio-pci.c	hw/virtio-pci: fix virtio behaviour	2016-07-29 00:07:10 +03:00
virtio-pci.h	hw/virtio-pci: fix virtio behaviour	2016-07-29 00:07:10 +03:00
virtio-rng.c	virtio-rng: Wrap in vmstate	2016-07-21 20:44:20 +03:00
virtio.c	virtio: check vring descriptor buffer length	2016-07-29 00:07:10 +03:00