qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>, Max Reitz <mreitz@redhat.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 3/9] virtio-9p: handle handle_9p_output() error
Date: Mon, 26 Sep 2016 17:21:41 +0100	[thread overview]
Message-ID: <20160926162141.GB25705@stefanha-x1.localdomain> (raw)
In-Reply-To: <147487885500.6679.17365810852820160326.stgit@bahia>

[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]

On Mon, Sep 26, 2016 at 10:34:15AM +0200, Greg Kurz wrote:
> 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>
> ---
> v3: - dropped the out_num check (already covered by iov_to_buf())
>     - reworded the in_num error message
>     - added an error path to detach and free the virtqueue element
> 
> I haven't added the R-b tags received during v2 because of the above
> changes.
> ---
>  hw/9pfs/virtio-9p-device.c |   26 +++++++++++++++++++++-----
>  1 file changed, 21 insertions(+), 5 deletions(-)

Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2016-09-26 16:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26  8:33 [Qemu-devel] [PATCH v3 0/9] virtio: avoid inappropriate QEMU termination Greg Kurz
2016-09-26  8:33 ` [Qemu-devel] [PATCH v3 1/9] virtio-9p: add parentheses to sizeof operator Greg Kurz
2016-09-26  8:34 ` [Qemu-devel] [PATCH v3 2/9] virtio-blk: make some functions static Greg Kurz
2016-09-26 16:15   ` Stefan Hajnoczi
2016-09-26  8:34 ` [Qemu-devel] [PATCH v3 3/9] virtio-9p: handle handle_9p_output() error Greg Kurz
2016-09-26 16:21   ` Stefan Hajnoczi [this message]
2016-09-26  8:34 ` [Qemu-devel] [PATCH v3 4/9] virtio-blk: handle virtio_blk_handle_request() errors Greg Kurz
2016-09-26 16:24   ` Stefan Hajnoczi
2016-09-26  8:34 ` [Qemu-devel] [PATCH v3 5/9] virtio-net: handle virtio_net_handle_ctrl() error Greg Kurz
2016-09-26 16:25   ` Stefan Hajnoczi
2016-09-26  8:34 ` [Qemu-devel] [PATCH v3 6/9] virtio-net: handle virtio_net_receive() errors Greg Kurz
2016-09-26 16:27   ` Stefan Hajnoczi
2016-09-26  8:34 ` [Qemu-devel] [PATCH v3 7/9] virtio-net: handle virtio_net_flush_tx() errors Greg Kurz
2016-09-26 16:28   ` Stefan Hajnoczi
2016-09-26  8:34 ` [Qemu-devel] [PATCH v3 8/9] virtio-scsi: convert virtio_scsi_bad_req() to use virtio_error() Greg Kurz
2016-09-26 16:35   ` Stefan Hajnoczi
2016-09-26 19:25     ` Greg Kurz
2016-09-26  8:35 ` [Qemu-devel] [PATCH v3 9/9] virtio-scsi: handle virtio_scsi_set_config() error Greg Kurz
2016-09-26 16:36   ` Stefan Hajnoczi
2016-09-26  9:00 ` [Qemu-devel] [PATCH v3 0/9] virtio: avoid inappropriate QEMU termination no-reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160926162141.GB25705@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=groug@kaod.org \
    --cc=jasowang@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).