From: Stefan Hajnoczi <stefanha@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/5] Clean up around bdrv_getlength()
Date: Fri, 9 May 2014 14:29:47 +0200 [thread overview]
Message-ID: <20140509122947.GB26017@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1399628898-3241-1-git-send-email-armbru@redhat.com>
On Fri, May 09, 2014 at 11:48:13AM +0200, Markus Armbruster wrote:
> Issues addressed in this series:
>
> * BlockDriver method bdrv_getlength() generally returns -errno, but
> some implementations return -1 instead. Fix them [PATCH 1].
>
> * Frequent conversions between sectors and bytes complicate the code
> needlessly. Clean up some [PATCH 2+3].
>
> * bdrv_getlength() always returns a multiple of BDRV_SECTOR_SIZE, but
> some places appear to be confused about that, and align the result
> up or down. Don't [PATCH 4].
>
> * bdrv_get_geometry() hides errors. Don't use it in places where
> errors should be detected [PATCH 5].
>
> Issues not addressed:
>
> * There are quite a few literals left in the code where
> BDRV_SECTOR_SIZE, BDRV_SECTOR_BITS or BDRV_SECTOR_MASK should be
> used instead.
>
> * Error handling is missing in places, but it's not always obvious
> whether errors can actually happen, and if yes, how to handle them.
>
> Markus Armbruster (5):
> raw-posix: Fix raw_getlength() to always return -errno on error
> block: New bdrv_nb_sectors()
> block: Use bdrv_nb_sectors() when sectors, not bytes are wanted
> block: Drop superfluous aligning of bdrv_getlength()'s value
> block: Avoid bdrv_get_geometry() where errors should be detected
>
> block-migration.c | 9 +++--
> block.c | 81 ++++++++++++++++++++++++--------------------
> block/qapi.c | 14 +++++---
> block/qcow2.c | 3 +-
> block/raw-posix.c | 28 ++++++++++++----
> block/vmdk.c | 5 ++-
> include/block/block.h | 1 +
> qemu-img.c | 93 ++++++++++++++++++++++++++++++++++-----------------
> 8 files changed, 147 insertions(+), 87 deletions(-)
>
> --
> 1.8.1.4
>
>
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
next prev parent reply other threads:[~2014-05-09 12:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 9:48 [Qemu-devel] [PATCH 0/5] Clean up around bdrv_getlength() Markus Armbruster
2014-05-09 9:48 ` [Qemu-devel] [PATCH 1/5] raw-posix: Fix raw_getlength() to always return -errno on error Markus Armbruster
2014-05-09 9:48 ` [Qemu-devel] [PATCH 2/5] block: New bdrv_nb_sectors() Markus Armbruster
2014-05-12 11:11 ` Kevin Wolf
2014-05-12 12:36 ` Markus Armbruster
2014-05-12 12:50 ` Eric Blake
2014-05-09 9:48 ` [Qemu-devel] [PATCH 3/5] block: Use bdrv_nb_sectors() when sectors, not bytes are wanted Markus Armbruster
2014-05-09 16:27 ` Markus Armbruster
2014-05-09 9:48 ` [Qemu-devel] [PATCH 4/5] block: Drop superfluous aligning of bdrv_getlength()'s value Markus Armbruster
2014-05-09 9:48 ` [Qemu-devel] [PATCH 5/5] block: Avoid bdrv_get_geometry() where errors should be detected Markus Armbruster
2014-05-09 12:29 ` Stefan Hajnoczi [this message]
2014-05-09 15:30 ` [Qemu-devel] [PATCH 0/5] Clean up around bdrv_getlength() 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=20140509122947.GB26017@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=armbru@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 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).