All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Benoît Canet" <benoit.canet@nodalink.com>
Subject: Re: [Qemu-devel] [PATCH v7 08/13] qcow2: Fix refcount blocks beyond image end
Date: Wed, 22 Oct 2014 11:28:06 +0200	[thread overview]
Message-ID: <544778A6.4020904@redhat.com> (raw)
In-Reply-To: <20141022092418.GE3188@noname.str.redhat.com>

On 2014-10-22 at 11:24, Kevin Wolf wrote:
> Am 22.10.2014 um 10:08 hat Max Reitz geschrieben:
>> If the qcow2 check function detects a refcount block located beyond the
>> image end, grow the image appropriately. This cannot break anything and
>> is the logical fix for such a case.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>>   block/qcow2-refcount.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++----
>>   1 file changed, 59 insertions(+), 4 deletions(-)
>>
>> diff --git a/block/qcow2-refcount.c b/block/qcow2-refcount.c
>> index d484029..3800d3c 100644
>> --- a/block/qcow2-refcount.c
>> +++ b/block/qcow2-refcount.c
>> @@ -1544,7 +1544,8 @@ static int check_refblocks(BlockDriverState *bs, BdrvCheckResult *res,
>>                              int64_t *nb_clusters)
>>   {
>>       BDRVQcowState *s = bs->opaque;
>> -    int64_t i;
>> +    int64_t i, size;
>> +    int ret;
>>   
>>       for(i = 0; i < s->refcount_table_size; i++) {
>>           uint64_t offset, cluster;
>> @@ -1560,9 +1561,63 @@ static int check_refblocks(BlockDriverState *bs, BdrvCheckResult *res,
>>           }
>>   
>>           if (cluster >= *nb_clusters) {
>> -            fprintf(stderr, "ERROR refcount block %" PRId64
>> -                    " is outside image\n", i);
>> -            res->corruptions++;
>> +            fprintf(stderr, "%s refcount block %" PRId64 " is outside image\n",
>> +                    fix & BDRV_FIX_ERRORS ? "Repairing" : "ERROR", i);
>> +
>> +            if (fix & BDRV_FIX_ERRORS) {
>> +                int64_t old_nb_clusters = *nb_clusters;
>> +
>> +                if (offset + s->cluster_size < offset ||
>> +                    offset > INT64_MAX - s->cluster_size)
> Do you still need the first condition with the reworked second one?

Right, we can drop it.

Max

>> +                {
>> +                    ret = -EINVAL;
>> +                    goto resize_fail;
>> +                }
> Kevin

  reply	other threads:[~2014-10-22  9:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  8:08 [Qemu-devel] [PATCH v7 00/13] qcow2: Fix image repairing Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 01/13] block: Add qemu_{, try_}blockalign0() Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 02/13] qcow2: Calculate refcount block entry count Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 03/13] qcow2: Fix leaks in dirty images Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 04/13] qcow2: Split qcow2_check_refcounts() Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 05/13] qcow2: Use sizeof(**refcount_table) Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 06/13] qcow2: Pull check_refblocks() up Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 07/13] qcow2: Reuse refcount table in calculate_refcounts() Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 08/13] qcow2: Fix refcount blocks beyond image end Max Reitz
2014-10-22  9:24   ` Kevin Wolf
2014-10-22  9:28     ` Max Reitz [this message]
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 09/13] qcow2: Do not perform potentially damaging repairs Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 10/13] qcow2: Rebuild refcount structure during check Max Reitz
2014-10-22  9:14   ` Kevin Wolf
2014-10-22  9:15     ` Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 11/13] qcow2: Clean up after refcount rebuild Max Reitz
2014-10-22  9:19   ` Kevin Wolf
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 12/13] iotests: Fix test outputs Max Reitz
2014-10-22  8:08 ` [Qemu-devel] [PATCH v7 13/13] iotests: Add test for potentially damaging repairs Max Reitz

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=544778A6.4020904@redhat.com \
    --to=mreitz@redhat.com \
    --cc=benoit.canet@nodalink.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 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.