From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
qemu-block@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: Drop bdrv_ioctl_bh_cb
Date: Wed, 1 Jun 2016 10:10:05 +0200 [thread overview]
Message-ID: <0e6d20b4-db2a-4966-e591-f4c1d09015fa@redhat.com> (raw)
In-Reply-To: <20160601015223.19277-1-famz@redhat.com>
On 01/06/2016 03:52, Fam Zheng wrote:
> 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>
> ---
> block/io.c | 20 ++------------------
> 1 file changed, 2 insertions(+), 18 deletions(-)
>
> diff --git a/block/io.c b/block/io.c
> index 2d832aa..c32f5b7 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -2309,19 +2309,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;
> @@ -2339,11 +2326,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:
>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2016-06-01 8:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 1:52 [Qemu-devel] [PATCH] block: Drop bdrv_ioctl_bh_cb Fam Zheng
2016-06-01 8:10 ` Paolo Bonzini [this message]
2016-06-01 19:48 ` Stefan Hajnoczi
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=0e6d20b4-db2a-4966-e591-f4c1d09015fa@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--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).