[adding some cc's]

On 04/21/2017 02:17 AM, Wouter Verhelst wrote:

> Side note though, while checking my OPT_INFO implementation, I
> encountered a problem. I ran your qemu-nbd like so:
> 
> ./qemu-nbd -x foo -D "test image" -t -p 18909 test.img
> 
> and then ran my nbd-client against it several times. At one point, I got
> a SIGPIPE, because of:
> 
> qemu-nbd: io/channel.c:306: qio_channel_yield: Assertion 
> `!ioc->read_coroutine' failed.

This may be an issue that we are already aware of on qemu; I also know
that Paolo has patches lined up that rework control flow in qemu-nbd to
be a bit more efficient in lock handling that may clear it up.  But if
it's something we haven't seen yet, I appreciate you reporting the test
case.

> 
> this was during a debugging session, so there have been a few times where
> I hit "k" in gdb, so the client was killed and the socket aborted. I'm
> not sure whether that's related, but it could be -- and I thought you'd
> want to know this.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nbd-general mailing list
Nbd-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nbd-general

Reply via email to