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

…

trace-events

…

vhost-backend.c

…

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-mmio.c

…

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.c

virtio: check vring descriptor buffer length

2016-07-29 00:07:10 +03:00