qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, den@virtuozzo.com, stefanha@redhat.com,
	vsementsov@yandex-team.ru, kwolf@redhat.com, hreitz@redhat.com
Subject: [PATCH v9 02/12] parallels: Fix high_off calculation in parallels_co_check()
Date: Tue, 31 Jan 2023 11:27:26 +0100	[thread overview]
Message-ID: <20230131102736.2127945-3-alexander.ivanov@virtuozzo.com> (raw)
In-Reply-To: <20230131102736.2127945-1-alexander.ivanov@virtuozzo.com>

Don't let high_off be more than the file size even if we don't fix the
image.

Signed-off-by: Alexander Ivanov <alexander.ivanov@virtuozzo.com>
Reviewed-by: Denis V. Lunev <den@openvz.org>
---
 block/parallels.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/block/parallels.c b/block/parallels.c
index 4af68adc61..436b36bbd9 100644
--- a/block/parallels.c
+++ b/block/parallels.c
@@ -460,12 +460,12 @@ static int coroutine_fn parallels_co_check(BlockDriverState *bs,
                     fix & BDRV_FIX_ERRORS ? "Repairing" : "ERROR", i);
             res->corruptions++;
             if (fix & BDRV_FIX_ERRORS) {
-                prev_off = 0;
                 s->bat_bitmap[i] = 0;
                 res->corruptions_fixed++;
                 flush_bat = true;
-                continue;
             }
+            prev_off = 0;
+            continue;
         }
 
         res->bfi.allocated_clusters++;
-- 
2.34.1



  parent reply	other threads:[~2023-01-31 10:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 10:27 [PATCH v9 00/11] parallels: Refactor the code of images checks and fix a bug Alexander Ivanov
2023-01-31 10:27 ` [PATCH v9 01/12] parallels: Out of image offset in BAT leads to image inflation Alexander Ivanov
2023-01-31 10:27 ` Alexander Ivanov [this message]
2023-01-31 10:27 ` [PATCH v9 03/12] parallels: Fix image_end_offset and data_end after out-of-image check Alexander Ivanov
2023-01-31 13:43   ` Denis V. Lunev
2023-01-31 10:27 ` [PATCH v9 04/12] parallels: create parallels_set_bat_entry_helper() to assign BAT value Alexander Ivanov
2023-01-31 10:27 ` [PATCH v9 05/12] parallels: Use generic infrastructure for BAT writing in parallels_co_check() Alexander Ivanov
2023-01-31 10:27 ` [PATCH v9 06/12] parallels: Move check of unclean image to a separate function Alexander Ivanov
2023-01-31 10:27 ` [PATCH v9 07/12] parallels: Move check of cluster outside " Alexander Ivanov
2023-01-31 15:29   ` Denis V. Lunev
2023-01-31 10:27 ` [PATCH v9 08/12] parallels: Fix statistics calculation Alexander Ivanov
2023-01-31 15:34   ` Denis V. Lunev
2023-01-31 10:27 ` [PATCH v9 09/12] parallels: Move check of leaks to a separate function Alexander Ivanov
2023-01-31 15:36   ` Denis V. Lunev
2023-01-31 10:27 ` [PATCH v9 10/12] parallels: Move statistic collection " Alexander Ivanov
2023-01-31 10:27 ` [PATCH v9 11/12] parallels: Replace qemu_co_mutex_lock by WITH_QEMU_LOCK_GUARD Alexander Ivanov
2023-01-31 10:27 ` [PATCH v9 12/12] parallels: Incorrect condition in out-of-image check Alexander Ivanov
2023-01-31 15:37   ` Denis V. Lunev

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=20230131102736.2127945-3-alexander.ivanov@virtuozzo.com \
    --to=alexander.ivanov@virtuozzo.com \
    --cc=den@virtuozzo.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    /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).