From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.1] block: Fix bdrv_is_allocated() return value
Date: Mon, 07 Jul 2014 09:50:54 -0600 [thread overview]
Message-ID: <53BAC1DE.50708@redhat.com> (raw)
In-Reply-To: <1404747446-10215-1-git-send-email-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
On 07/07/2014 09:37 AM, Kevin Wolf wrote:
> bdrv_is_allocated() should return either 0 or 1 in successful cases.
> We're lucky that currently, the callers that rely on this (e.g. because
> they check for ret == 1) don't seem to break badly. They just might skip
> some optimisation or in the case of qemu-io 'map' print separate lines
> where a single line would suffice. In theory, a wrong allocation status
> could lead to image corruption with certain operations, so let's fix
> this quickly.
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block.c b/block.c
> index f80e2b2..e2e9cbb 100644
> --- a/block.c
> +++ b/block.c
> @@ -4039,7 +4039,7 @@ int coroutine_fn bdrv_is_allocated(BlockDriverState *bs, int64_t sector_num,
> if (ret < 0) {
> return ret;
> }
> - return (ret & BDRV_BLOCK_ALLOCATED);
> + return !!(ret & BDRV_BLOCK_ALLOCATED);
Reviewed-by: Eric Blake <eblake@redhat.com>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-07-07 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 15:37 [Qemu-devel] [PATCH for-2.1] block: Fix bdrv_is_allocated() return value Kevin Wolf
2014-07-07 15:50 ` Eric Blake [this message]
2014-07-08 12:57 ` 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=53BAC1DE.50708@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.