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 6/9] virtio-net: handle virtio_net_receive() errors
Date: Mon, 26 Sep 2016 17:27:09 +0100	[thread overview]
Message-ID: <20160926162709.GE25705@stefanha-x1.localdomain> (raw)
In-Reply-To: <147487888056.6679.17541794925955609666.stgit@bahia>

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

On Mon, Sep 26, 2016 at 10:34:40AM +0200, Greg Kurz wrote:
> All these errors are caused by a buggy guest: let's switch the device to
> the broken state instead of terminating QEMU. Also we detach the element
> from the virtqueue and free it.
> 
> Signed-off-by: Greg Kurz <groug@kaod.org>
> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> ---
> v3: - detach and free element
>     - updated changelog
> ---
>  hw/net/virtio-net.c |   27 +++++++++++++++------------
>  1 file changed, 15 insertions(+), 12 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:27 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
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 [this message]
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=20160926162709.GE25705@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).