From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Federico Simoncelli <fsimonce@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: add the optional file entry to query-block
Date: Mon, 1 Jul 2013 10:34:34 +0200 [thread overview]
Message-ID: <20130701083434.GA9000@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <51CDE4D7.7090402@redhat.com>
Am 28.06.2013 um 21:32 hat Eric Blake geschrieben:
> On 06/28/2013 08:32 AM, Federico Simoncelli wrote:
> > This patch adds the optional file entry to the query-block output.
> > The value is a json-object representing the information about the
> > underlying file or device (when present).
> >
> > Signed-off-by: Federico Simoncelli <fsimonce@redhat.com>
> > ---
> > block/qapi.c | 9 ++++++++-
> > qapi-schema.json | 4 +++-
> > qmp-commands.hx | 8 ++++++++
> > tests/qemu-iotests/043.out | 15 +++++++++++++++
> > 4 files changed, 34 insertions(+), 2 deletions(-)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> > +++ b/block/qapi.c
> > @@ -119,7 +119,7 @@ void bdrv_query_image_info(BlockDriverState *bs,
> >
> > info->filename = g_strdup(bs->filename);
> > info->format = g_strdup(bdrv_get_format_name(bs));
> > - info->virtual_size = total_sectors * 512;
> > + info->virtual_size = bdrv_getlength(bs);
>
> This change seems independently useful, but I'm not sure if it's worth
> splitting out into a separate patch.
It probably is, because (a) it's a separate logical change and (b) this
isn't entirely correct. bdrv_getlength() can fail, so we need to do more
than just changing this one line. If bdrv_getlength() fails we should
error out instead of outputting a negative size.
Kevin
next prev parent reply other threads:[~2013-07-01 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 14:32 [Qemu-devel] [PATCH] block: add the optional file entry to query-block Federico Simoncelli
2013-06-28 19:32 ` Eric Blake
2013-07-01 8:34 ` Kevin Wolf [this message]
2013-07-02 8:52 ` 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=20130701083434.GA9000@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=fsimonce@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).