qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: qemu-block@nongnu.org
Cc: codyprime@gmail.com, kwolf@redhat.com, mreitz@redhat.com,
	jhf@kamp.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2] block/vhdx: add check for truncated image files
Date: Tue, 3 Sep 2019 11:09:59 +0200	[thread overview]
Message-ID: <7d08ff22-ebe9-92f3-82a0-3168f30f2612@kamp.de> (raw)
In-Reply-To: <20190902152413.14070-1-pl@kamp.de>

Am 02.09.19 um 17:24 schrieb Peter Lieven:
> qemu is currently not able to detect truncated vhdx image files.
> Add a basic check if all allocated blocks are reachable at open and
> report all errors during bdrv_co_check.
>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> V2: - add error reporting [Kevin]
>      - use bdrv_getlength instead of bdrv_get_allocated_file_size [Kevin]
>      - factor out BAT entry check and add error reporting for region
>        overlaps
>      - already check on vhdx_open
>
>   block/vhdx.c | 85 +++++++++++++++++++++++++++++++++++++++++-----------
>   1 file changed, 68 insertions(+), 17 deletions(-)
>
> diff --git a/block/vhdx.c b/block/vhdx.c
> index 6a09d0a55c..6afba5e8c2 100644
> --- a/block/vhdx.c
> +++ b/block/vhdx.c
> @@ -24,6 +24,7 @@
>   #include "qemu/option.h"
>   #include "qemu/crc32c.h"
>   #include "qemu/bswap.h"
> +#include "qemu/error-report.h"
>   #include "vhdx.h"
>   #include "migration/blocker.h"
>   #include "qemu/uuid.h"
> @@ -235,6 +236,9 @@ static int vhdx_region_check(BDRVVHDXState *s, uint64_t start, uint64_t length)
>       end = start + length;
>       QLIST_FOREACH(r, &s->regions, entries) {
>           if (!((start >= r->end) || (end <= r->start))) {
> +            error_report("VHDX region %" PRIu64 "-%" PRIu64 " overlaps with "
> +                         "region %" PRIu64 "-%." PRIu64, start, end, r->start,
> +                         r->end);
>               ret = -EINVAL;
>               goto exit;
>           }
> @@ -877,6 +881,60 @@ static void vhdx_calc_bat_entries(BDRVVHDXState *s)
>   
>   }
>   
> +static int vhdx_check_bat_entries(BlockDriverState *bs, int *errcnt)
> +{
> +    BDRVVHDXState *s = bs->opaque;
> +    int64_t image_file_size = bdrv_getlength(bs->file->bs);
> +    uint64_t payblocks = s->chunk_ratio;
> +    int i, ret = 0;
> +
> +    for (i = 0; i < s->bat_entries; i++) {
> +        if ((s->bat[i] & VHDX_BAT_STATE_BIT_MASK) ==
> +            PAYLOAD_BLOCK_FULLY_PRESENT) {
> +            /*
> +             * Check if fully allocated BAT entries do not reside after
> +             * end of the image file.
> +             */
> +            if ((s->bat[i] & VHDX_BAT_FILE_OFF_MASK) + s->block_size >
> +                image_file_size) {
> +                error_report("VHDX BAT entry %d offset points after end of "
> +                             "file. Image has probably been truncated.", i);
> +                ret = -EINVAL;
> +                if (!errcnt) {
> +                    break;
> +                }
> +                (*errcnt)++;
> +            }
> +
> +            /*
> +             * verify populated BAT field file offsets against
> +             * region table and log entries
> +             */
> +            if (payblocks--) {
> +                /* payload bat entries */
> +                int ret2;
> +                ret2 = vhdx_region_check(s, s->bat[i] & VHDX_BAT_FILE_OFF_MASK,
> +                                         s->block_size);
> +                if (ret2 < 0) {
> +                    ret = -EINVAL;
> +                    if (errcnt) {
> +                        break;
> +                    }


This should be if (!errcnt) ...


I will respin, but wait for feedback regarding the remainder of the patch.


Peter





  reply	other threads:[~2019-09-03  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-02 15:24 [Qemu-devel] [PATCH V2] block/vhdx: add check for truncated image files Peter Lieven
2019-09-03  9:09 ` Peter Lieven [this message]
2019-09-03 13:02 ` Kevin Wolf
2019-09-03 13:10   ` Peter Lieven
2019-09-03 13:27     ` 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=7d08ff22-ebe9-92f3-82a0-3168f30f2612@kamp.de \
    --to=pl@kamp.de \
    --cc=codyprime@gmail.com \
    --cc=jhf@kamp.de \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).