From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ping Fan Liu <pingfank@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] aio: fix qemu_bh_schedule() bh->ctx race condition
Date: Wed, 4 Jun 2014 09:55:37 +0200 [thread overview]
Message-ID: <20140604075537.GA21259@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <538DC518.8080007@profihost.ag>
On Tue, Jun 03, 2014 at 02:52:40PM +0200, Stefan Priebe - Profihost AG wrote:
> Tested-by: Stefan Priebe <s.priebe@profihost.ag>
Thanks!
prev parent reply other threads:[~2014-06-04 7:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 9:21 [Qemu-devel] [PATCH] aio: fix qemu_bh_schedule() bh->ctx race condition Stefan Hajnoczi
2014-06-03 11:12 ` Paolo Bonzini
2014-06-03 12:49 ` Stefan Hajnoczi
2014-06-03 12:52 ` Stefan Priebe - Profihost AG
2014-06-04 7:55 ` Stefan Hajnoczi [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=20140604075537.GA21259@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=pbonzini@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=s.priebe@profihost.ag \
--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).