From: Stefan Priebe <s.priebe@profihost.ag>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: stefanha@gmail.com, ceph-devel@vger.kernel.org,
qemu-devel@nongnu.org, josh durgin <josh.durgin@inktank.com>
Subject: Re: [Qemu-devel] [PATCHv4] rbd block driver fix race between aio completition and aio cancel
Date: Thu, 29 Nov 2012 22:38:51 +0100 [thread overview]
Message-ID: <50B7D5EB.5030105@profihost.ag> (raw)
In-Reply-To: <249699163.16251603.1354202609373.JavaMail.root@redhat.com>
Hi Paolo,
Am 29.11.2012 16:23, schrieb Paolo Bonzini:
>> + qemu_vfree(acb->bounce);
>
> This vfree is not needed, since the BH will run and do the free.
new patch v5 sent.
Greets,
Stefan
prev parent reply other threads:[~2012-11-29 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 14:28 [Qemu-devel] [PATCHv4] rbd block driver fix race between aio completition and aio cancel Stefan Priebe
2012-11-29 15:23 ` Paolo Bonzini
2012-11-29 21:38 ` Stefan Priebe [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=50B7D5EB.5030105@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).