aboutsummaryrefslogtreecommitdiff
path: root/qobject/qint.c
diff options
context:
space:
mode:
authorGreg Kurz <groug@kaod.org>2016-09-30 17:12:58 +0200
committerMichael S. Tsirkin <mst@redhat.com>2016-10-10 01:16:59 +0300
commitd3d74d6fe095e2e49d030e0c163cecfb9c20f1d4 (patch)
tree81c32efd43e80a2f8803fb81e32e260512454b23 /qobject/qint.c
parentd14dde5ec7a38df2e00a6f1b58e96ba38359dbb0 (diff)
virtio-9p: handle handle_9p_output() error
A broken guest may send a request without providing buffers for the reply or for the request itself, and virtqueue_pop() will return an element with either in_num == 0 or out_num == 0. All 9P requests are expected to start with the following 7-byte header: uint32_t size_le; uint8_t id; uint16_t tag_le; If iov_to_buf() fails to return these 7 bytes, then something is wrong in the guest. In both cases, it is wrong to crash QEMU, since the root cause lies in the guest. This patch hence does the following: - keep the check of in_num since pdu_complete() assumes it has enough space to store the reply and we will send something broken to the guest - let iov_to_buf() handle out_num == 0, since it will return 0 just like if the guest had provided an zero-sized buffer. - call virtio_error() to inform the guest that the device is now broken, instead of aborting - detach the request from the virtqueue and free it Signed-off-by: Greg Kurz <groug@kaod.org> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'qobject/qint.c')
0 files changed, 0 insertions, 0 deletions