qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Thibaut Collet <thibaut.collet@6wind.com>
Cc: jasowang@redhat.com, qemu-devel@nongnu.org, v.maffione@gmail.com,
	stefanha@redhat.com, g.lettieri@iet.unipi.it, rizzo@iet.unipi.it
Subject: Re: [Qemu-devel] [PATCH 1/1] net: fix queue's purge on VM stop
Date: Fri, 29 May 2015 14:12:09 +0100	[thread overview]
Message-ID: <20150529131209.GJ8598@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1432800194-1192-1-git-send-email-thibaut.collet@6wind.com>

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

On Thu, May 28, 2015 at 10:03:14AM +0200, Thibaut Collet wrote:
> For netdev backend with no receive callback, packets must not be enqueued. When
> VM stops the enqueued packets are purged (see fixes ca77d85e1dbf). That causes a
> qemu segfault due to a call of a NULL pointer function.

virtio-net NIC <-> vhost-user should bypass the QEMU net subsystem since
rx/tx virtqueues are handled outside the QEMU process.  Who is enqueuing
packets on vhost-user's incoming_queue?

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-05-29 13:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  8:03 [Qemu-devel] [PATCH 1/1] net: fix queue's purge on VM stop Thibaut Collet
2015-05-29 13:12 ` Stefan Hajnoczi [this message]
2015-05-29 14:28   ` Thibaut Collet
2015-06-02 10:34     ` Stefan Hajnoczi
2015-06-03  7:56       ` Thibaut Collet
2015-06-03  9:42         ` Jason Wang
2015-06-03 13:40           ` Stefan Hajnoczi
2015-06-04  9:35             ` Jason Wang
2015-06-05 13:24               ` [Qemu-devel] [PATCH v2] net: Add support of VIRTIO_NET_F_GUEST_ANNOUNCE for vhost-net/vhost-user Thibaut Collet
2015-06-08  5:55                 ` Jason Wang
2015-06-08  8:21                   ` Thibaut Collet
2015-06-08  9:14                     ` Jason Wang
2015-06-08 10:01                       ` Thibaut Collet
2015-06-08 10:09                         ` Michael S. Tsirkin
2015-06-08 10:22                         ` Jason Wang
2015-06-08 13:32                     ` Stefan Hajnoczi
2015-06-08 14:05                       ` Thibaut Collet
2015-06-08 15:13                         ` Stefan Hajnoczi
2015-06-08 15:32                           ` Thibaut Collet
2015-06-09 10:38                             ` Stefan Hajnoczi
2015-06-09 10:43                             ` Stefan Hajnoczi
2015-06-08 16:13                           ` Michael S. Tsirkin
2015-06-09  2:35                             ` Jason Wang
2015-06-08 10:12                 ` Michael S. Tsirkin
2015-06-08 11:29                   ` Thibaut Collet
2015-06-08 12:45                     ` Michael S. Tsirkin
2015-06-08 13:20                       ` Thibaut Collet
2015-06-08 15:48                         ` Michael S. Tsirkin
2015-06-08 13:25                 ` Stefan Hajnoczi
2015-06-03  9:42         ` [Qemu-devel] [PATCH 1/1] net: fix queue's purge on VM stop Stefan Hajnoczi
2015-06-01  9:17 ` Jason Wang
2015-06-01 10:14   ` Thibaut Collet
2015-06-03  9:40     ` Jason Wang

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=20150529131209.GJ8598@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=g.lettieri@iet.unipi.it \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rizzo@iet.unipi.it \
    --cc=stefanha@redhat.com \
    --cc=thibaut.collet@6wind.com \
    --cc=v.maffione@gmail.com \
    /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).