From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
qemu block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] nbd-client: fix hang after server closes connection
Date: Wed, 23 Aug 2017 09:28:53 -0500 [thread overview]
Message-ID: <63c24596-1f48-5f43-6b4d-8709b5c40036@redhat.com> (raw)
In-Reply-To: <aa8ea653-0ec1-90bb-f8ef-71511dab0a9a@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
On 08/23/2017 09:25 AM, Eric Blake wrote:
> On 08/21/2017 02:01 PM, Eric Blake wrote:
>> On 08/21/2017 11:27 AM, Stefan Hajnoczi wrote:
>>> On Mon, Aug 21, 2017 at 5:15 PM, Stefan Hajnoczi <stefanha@redhat.com> wrote:
>>>> (qemu) quit
>>>> ...hang...
>>>
>>> By the way, the same issue is present in QEMU 2.9. This is not a 2.10
>>> regression.
>>
>> Most likely, though, it IS a regression introduced in 2.9 and not
>> present in 2.8. I'll add this to my list of 2.11 NBD patches.
>
> Since it looks like we're doing -rc4 and including other NBD patches for
> that, I'm adding this to my 2.10 NBD queue,
On IRC, Stefan informed me that 'nbd-client: avoid spurious
qio_channel_yield() re-entry' obsoletes this one.
> and will send a pull request
> shortly...
This part is still true
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-23 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 16:15 [Qemu-devel] [PATCH] nbd-client: fix hang after server closes connection Stefan Hajnoczi
2017-08-21 16:27 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-08-21 19:01 ` Eric Blake
2017-08-23 14:25 ` Eric Blake
2017-08-23 14:28 ` Eric Blake [this message]
2017-08-22 13:49 ` [Qemu-devel] " Philippe Mathieu-Daudé
2017-08-23 14:46 ` Stefan Hajnoczi
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=63c24596-1f48-5f43-6b4d-8709b5c40036@redhat.com \
--to=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@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).