From: Wen Congyang <wency@cn.fujitsu.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: pbonzini@redhat.com, crobinso@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, eharney@redhat.com
Subject: Re: [Qemu-devel] [PATCH] raw-posix: Fix .bdrv_co_get_block_status() for unaligned image size
Date: Tue, 9 Jun 2015 17:47:36 +0800 [thread overview]
Message-ID: <5576B638.8000907@cn.fujitsu.com> (raw)
In-Reply-To: <1433840108-9996-1-git-send-email-kwolf@redhat.com>
On 06/09/2015 04:55 PM, Kevin Wolf wrote:
> Image files with an unaligned image size have a final hole that starts
> at EOF, i.e. in the middle of a sector. Currently, *pnum == 0 is
> returned when checking the status of this sector. In qemu-img, this
> triggers an assertion failure.
>
> In order to fix this, one type for the sector that contains EOF must be
> found. Treating a hole as data is safe, so this patch rounds the
> calculated number of data sectors up, so that a partial sector at EOF is
> treated as a full data sector.
>
> This fixes https://bugzilla.redhat.com/show_bug.cgi?id=1229394
>
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
> block/raw-posix.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/block/raw-posix.c b/block/raw-posix.c
> index 2990e95..44ade8c 100644
> --- a/block/raw-posix.c
> +++ b/block/raw-posix.c
> @@ -1848,8 +1848,9 @@ static int64_t coroutine_fn raw_co_get_block_status(BlockDriverState *bs,
> *pnum = nb_sectors;
> ret = BDRV_BLOCK_DATA;
> } else if (data == start) {
> - /* On a data extent, compute sectors to the end of the extent. */
> - *pnum = MIN(nb_sectors, (hole - start) / BDRV_SECTOR_SIZE);
> + /* On a data extent, compute sectors to the end of the extent,
> + * possibly including a partial sector at EOF. */
Not only for EOF. If the hole and start are in the same sector, (hole - start) / BDRV_SECTOR_SIZE
will be 0
> + *pnum = MIN(nb_sectors, DIV_ROUND_UP(hole - start, BDRV_SECTOR_SIZE));
> ret = BDRV_BLOCK_DATA;
> } else {
> /* On a hole, compute sectors to the beginning of the next extent. */
>
So, if start is hole, data and start are in the same sector, (data - start) / BDRV_SECTOR_SIZE
will be 0, you also need to fix it here.
Thanks
Wen Congyang
next prev parent reply other threads:[~2015-06-09 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 8:55 [Qemu-devel] [PATCH] raw-posix: Fix .bdrv_co_get_block_status() for unaligned image size Kevin Wolf
2015-06-09 9:47 ` Wen Congyang [this message]
2015-06-09 9:49 ` Kevin Wolf
2015-06-09 10:11 ` Wen Congyang
2015-06-09 11:36 ` Eric Blake
2015-06-09 14:14 ` Cole Robinson
2015-06-09 15:25 ` [Qemu-devel] [Qemu-block] " 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=5576B638.8000907@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=crobinso@redhat.com \
--cc=eharney@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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.