From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1.1 6/6] block: avoid useless checks on acb->bh
Date: Mon, 14 Nov 2011 17:50:54 +0100 [thread overview]
Message-ID: <1321289454-9219-7-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <1321289454-9219-1-git-send-email-pbonzini@redhat.com>
Coverity is confused by this "if" and reports leaks on acb->bh.
The bottom half is always deleted before releasing the AIOCB,
in either bdrv_aio_cancel_em or bdrv_aio_bh_cb.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
block.c | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/block.c b/block.c
index 05b0e2c..e847738 100644
--- a/block.c
+++ b/block.c
@@ -2490,9 +2490,7 @@ static BlockDriverAIOCB *bdrv_aio_rw_vector(BlockDriverState *bs,
acb->is_write = is_write;
acb->qiov = qiov;
acb->bounce = qemu_blockalign(bs, qiov->size);
-
- if (!acb->bh)
- acb->bh = qemu_bh_new(bdrv_aio_bh_cb, acb);
+ acb->bh = qemu_bh_new(bdrv_aio_bh_cb, acb);
if (is_write) {
qemu_iovec_to_buffer(acb->qiov, acb->bounce);
--
1.7.7.1
next prev parent reply other threads:[~2011-11-14 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 16:50 [Qemu-devel] [PATCH 1.1 0/6] block: drop useless checks for NULL Paolo Bonzini
2011-11-14 16:50 ` [Qemu-devel] [PATCH 1.1 1/6] block: bdrv_aio_* do not return NULL Paolo Bonzini
2011-11-14 16:50 ` [Qemu-devel] [PATCH 1.1 2/6] block: simplify failure handling for bdrv_aio_multiwrite Paolo Bonzini
2011-11-14 16:50 ` [Qemu-devel] [PATCH 1.1 3/6] block: qemu_aio_get does not return NULL Paolo Bonzini
2011-11-14 16:50 ` [Qemu-devel] [PATCH 1.1 4/6] dma: the passed io_func " Paolo Bonzini
2011-11-14 16:50 ` [Qemu-devel] [PATCH 1.1 5/6] block: dma_bdrv_* " Paolo Bonzini
2011-11-14 16:50 ` Paolo Bonzini [this message]
2011-11-30 8:12 ` [Qemu-devel] [PATCH 1.1 v2] block: bdrv_aio_* do " Paolo Bonzini
2011-11-30 8:12 ` [Qemu-devel] [PATCH 1.1 0/6] block: drop useless checks for NULL Paolo Bonzini
2011-12-05 16:56 ` Kevin Wolf
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=1321289454-9219-7-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).