qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Fam Zheng <famz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PULL 11/12] block: Drop bdrv_ioctl_bh_cb
Date: Tue,  7 Jun 2016 15:26:24 +0100	[thread overview]
Message-ID: <1465309585-31551-12-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1465309585-31551-1-git-send-email-stefanha@redhat.com>

From: Fam Zheng <famz@redhat.com>

Similar to the "!drv || !drv->bdrv_aio_ioctl" case above, here it is
okay to set co.ret and return. As pointed out by Paolo, a BH will be
created as necessary by the caller (bdrv_co_maybe_schedule_bh).
Besides, as pointed out by Kevin, "data" was leaked before.

Reported-by: Kevin Wolf <kwolf@redhat.com>
Reported-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Fam Zheng <famz@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-id: 20160601015223.19277-1-famz@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 block/io.c | 20 ++------------------
 1 file changed, 2 insertions(+), 18 deletions(-)

diff --git a/block/io.c b/block/io.c
index a2fba67..6070e77 100644
--- a/block/io.c
+++ b/block/io.c
@@ -2327,19 +2327,6 @@ int bdrv_discard(BlockDriverState *bs, int64_t sector_num, int nb_sectors)
     return rwco.ret;
 }
 
-typedef struct {
-    CoroutineIOCompletion *co;
-    QEMUBH *bh;
-} BdrvIoctlCompletionData;
-
-static void bdrv_ioctl_bh_cb(void *opaque)
-{
-    BdrvIoctlCompletionData *data = opaque;
-
-    bdrv_co_io_em_complete(data->co, -ENOTSUP);
-    qemu_bh_delete(data->bh);
-}
-
 static int bdrv_co_do_ioctl(BlockDriverState *bs, int req, void *buf)
 {
     BlockDriver *drv = bs->drv;
@@ -2357,11 +2344,8 @@ static int bdrv_co_do_ioctl(BlockDriverState *bs, int req, void *buf)
 
     acb = drv->bdrv_aio_ioctl(bs, req, buf, bdrv_co_io_em_complete, &co);
     if (!acb) {
-        BdrvIoctlCompletionData *data = g_new(BdrvIoctlCompletionData, 1);
-        data->bh = aio_bh_new(bdrv_get_aio_context(bs),
-                                bdrv_ioctl_bh_cb, data);
-        data->co = &co;
-        qemu_bh_schedule(data->bh);
+        co.ret = -ENOTSUP;
+        goto out;
     }
     qemu_coroutine_yield();
 out:
-- 
2.5.5

  parent reply	other threads:[~2016-06-07 14:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07 14:26 [Qemu-devel] [PULL 00/12] Block patches Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 01/12] tests: avoid coroutine pool test crash Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 02/12] blockdev-backup: Use bdrv_lookup_bs on target Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 03/12] blockdev-backup: Don't move target AioContext if it's attached Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 04/12] virtio-blk: Remove op blocker for dataplane Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 05/12] virtio-scsi: " Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 06/12] virtio: drop duplicate virtio_queue_get_id() function Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 07/12] block/io: Remove unused bdrv_aio_write_zeroes() Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 08/12] iostatus: fix comments for block_job_iostatus_reset Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 09/12] block/io: optimize bdrv_co_pwritev for small requests Stefan Hajnoczi
2016-06-07 14:26 ` [Qemu-devel] [PULL 10/12] block: Move BlockRequest type to io.c Stefan Hajnoczi
2016-06-07 14:26 ` Stefan Hajnoczi [this message]
2016-06-07 14:26 ` [Qemu-devel] [PULL 12/12] throttle: refuse iops-size without iops-total/read/write Stefan Hajnoczi
2016-06-07 15:34 ` [Qemu-devel] [PULL 00/12] Block patches Peter Maydell

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=1465309585-31551-12-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=famz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).