qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Andrey Korolyov <andrey@xdel.ru>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-stable] 2.1 unexpected stop after exporting blockdev via nbd server
Date: Thu, 08 Jan 2015 13:11:25 +0100	[thread overview]
Message-ID: <54AE73ED.1070105@redhat.com> (raw)
In-Reply-To: <CAJSP0QU4UYrZyEPT5Mvdboc5_vna5E0thKC+vYi9mybKfX1qkw@mail.gmail.com>



On 08/01/2015 11:31, Stefan Hajnoczi wrote:
> Excellent, please add the following commits to stable:
> f214928 nbd: Follow the BDS' AIO context
> 3338442 block: Add AIO context notifiers
> 958c717 nbd: Drop nbd_can_read()
> 
> They prevent crashes when the run-time NBD server is used together
> with virtio-blk dataplane.
> 
> They apply cleanly onto stable-2.1 and I have tested that the crash is solved.

I think they break Win32 compilation.  Didn't Max have to wait for me to
port socket AioContext handlers to Windows?

Paolo

  reply	other threads:[~2015-01-08 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 15:38 [Qemu-devel] 2.1 unexpected stop after exporting blockdev via nbd server Andrey Korolyov
2015-01-02 13:04 ` Stefan Hajnoczi
2015-01-05 13:12   ` Andrey Korolyov
2015-01-06 11:43     ` Stefan Hajnoczi
2015-01-06 11:49     ` Stefan Hajnoczi
2015-01-08  1:17       ` [Qemu-devel] [Qemu-stable] " Michael Roth
2015-01-08 10:31         ` Stefan Hajnoczi
2015-01-08 12:11           ` Paolo Bonzini [this message]
2015-01-08 13:25             ` 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=54AE73ED.1070105@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=andrey@xdel.ru \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=stefanha@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).