qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jens Freimann <jfreimann@redhat.com>
To: Marc-Andr?? Lureau <marcandre.lureau@gmail.com>
Cc: QEMU <qemu-devel@nongnu.org>,
	Victor Kaplansky <victork@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/5] libvhost-user: quit when no more data received
Date: Thu, 21 Sep 2017 18:05:10 +0200	[thread overview]
Message-ID: <20170921160510.h2b6kbtsvf3rc73z@localhost.localdomain> (raw)
In-Reply-To: <20170921133137.dbs6o6mwe6tm3joh@localhost.localdomain>

On Thu, Sep 21, 2017 at 01:31:37PM +0000, Jens Freimann wrote:
>On Wed, Sep 20, 2017 at 04:14:33PM +0000, Marc-Andr?? Lureau wrote:
>>On Wed, Sep 20, 2017 at 5:09 PM, Jens Freimann <jfreimann@redhat.com> wrote:
>>>On Tue, Sep 19, 2017 at 04:46:24PM +0000, Marc-Andr?? Lureau wrote:
>>>>On Tue, Aug 8, 2017 at 10:52 PM Jens Freimann <jfreimann@redhat.com>
>>>>wrote:
>>We want to treat disconnect as a panic condition imho, that the
>>library user is free to implement in different way (abort() clean
>>exit, reconnect etc).
>
>Ok, that wasn't obvious to me. Thanks for clarifying! So I was 
>"fixing" the wrong part. On a disconnect vubr_panic() in
>vhost-user-bridge.c is called and is supposed to do the right thing.
>
>Currently it will print an error message "PANIC: Unhandled request:

Actually it is "Error while recvmsg" because in vu_message_read()
vu_panic is called if rc from recvmsg is <= 0. Followed by "Error
while dispatching" printed by vhost-user-bridge. 

regards,
Jens 

  reply	other threads:[~2017-09-21 16:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 20:38 [Qemu-devel] [PATCH v2 0/5] tests/pxe-test: add testcase using vhost-user-bridge Jens Freimann
2017-08-08 20:38 ` [Qemu-devel] [PATCH v2 1/5] tests/vhost-user-bridge: disable debug output by default Jens Freimann
2017-08-08 20:38 ` [Qemu-devel] [PATCH v2 2/5] net: fix -netdev socket, fd= for UDP sockets Jens Freimann
2017-11-03 18:46   ` Peter Maydell
2017-11-06 10:49     ` Jens Freimann
2017-08-08 20:38 ` [Qemu-devel] [PATCH v2 3/5] libvhost-user: quit when no more data received Jens Freimann
2017-09-19 16:46   ` Marc-André Lureau
2017-09-20 15:09     ` Jens Freimann
2017-09-20 16:14       ` Marc-André Lureau
2017-09-21 13:31         ` Jens Freimann
2017-09-21 16:05           ` Jens Freimann [this message]
2017-08-08 20:38 ` [Qemu-devel] [PATCH v2 4/5] libqtest: always set up signal handler for SIGABRT Jens Freimann
2017-08-08 20:39 ` [Qemu-devel] [PATCH v2 5/5] tests/pxe-test: add testcase using vhost-user-bridge Jens Freimann
2017-08-08 21:05 ` [Qemu-devel] [PATCH for-2.10? v2 0/5] " Eric Blake
2017-08-08 22:18   ` Michael S. Tsirkin
2017-08-08 23:59 ` [Qemu-devel] [PATCH " no-reply
2017-08-09  1:17   ` Michael S. Tsirkin
2017-08-09  8:21     ` Jens Freimann

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=20170921160510.h2b6kbtsvf3rc73z@localhost.localdomain \
    --to=jfreimann@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=victork@redhat.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).