qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] Crash when using -daemonize
Date: Tue, 10 Mar 2015 10:35:00 +0100	[thread overview]
Message-ID: <54FEBAC4.30707@redhat.com> (raw)
In-Reply-To: <54FE11E6.3060904@de.ibm.com>



On 09/03/2015 22:34, Christian Borntraeger wrote:
> I think it is. 
> Paolo has posted a quick fix in the thread of "vl: take iothread lock very early".
> 
> Can you verify? 
> 
> Paolo, what is the status of this fix?
> 

Sending a pull request today with the proper fix.

Paolo

      parent reply	other threads:[~2015-03-10  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 21:03 [Qemu-devel] Crash when using -daemonize Stefan Berger
2015-03-09 21:34 ` Christian Borntraeger
2015-03-09 23:39   ` Stefan Berger
2015-03-10  9:35   ` Paolo Bonzini [this message]

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=54FEBAC4.30707@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@linux.vnet.ibm.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).