qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, eblake@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v2 6/7] block/qcow2-refcount: fix out-of-file L1 entries to be zero
Date: Mon, 8 Oct 2018 22:09:55 +0200	[thread overview]
Message-ID: <c0168aed-d00f-5af7-917b-a0824c9b270f@redhat.com> (raw)
In-Reply-To: <20180817122219.16206-7-vsementsov@virtuozzo.com>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

On 17.08.18 14:22, Vladimir Sementsov-Ogievskiy wrote:
> Zero out corrupted L1 table entry, which reference L2 table out of
> underlying file.
> Zero L1 table entry means that "the L2 table and all clusters described
> by this L2 table are unallocated."
> 
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
>  block/qcow2-refcount.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 44 insertions(+)

Hm.  The specification actually says nothing about offsets being allowed
past the end of the file, and I don't think we ever use them (outside of
a very short period during image creation, where we point to refcount
structures beyond the EOF).

So the patch looks OK to me, although I'd still prefer a separate
fprintf() and think it would be fine for check_refcounts_l1() to call
fix_table_entry() directly.

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-10-08 20:10 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 12:22 [Qemu-devel] [PATCH 0/7] qcow2 check improvements Vladimir Sementsov-Ogievskiy
2018-08-17 12:22 ` [Qemu-devel] [PATCH v2 1/7] block/qcow2-refcount: fix check_oflag_copied Vladimir Sementsov-Ogievskiy
2018-10-08 15:28   ` Max Reitz
2018-08-17 12:22 ` [Qemu-devel] [PATCH v2 2/7] block/qcow2-refcount: avoid eating RAM Vladimir Sementsov-Ogievskiy
2018-10-08 15:31   ` Max Reitz
2018-10-08 20:17     ` Vladimir Sementsov-Ogievskiy
2018-10-08 20:22     ` Vladimir Sementsov-Ogievskiy
2018-10-08 20:39       ` Max Reitz
2018-08-17 12:22 ` [Qemu-devel] [PATCH v2 3/7] block/qcow2-refcount: check_refcounts_l2: refactor compressed case Vladimir Sementsov-Ogievskiy
2018-10-08 15:40   ` Max Reitz
2018-08-17 12:22 ` [Qemu-devel] [PATCH v2 4/7] block/qcow2-refcount: check_refcounts_l2: reduce ignored overlaps Vladimir Sementsov-Ogievskiy
2018-10-08 15:44   ` Max Reitz
2018-08-17 12:22 ` [Qemu-devel] [PATCH v2 5/7] block/qcow2-refcount: check_refcounts_l2: split fix_l2_entry_to_zero Vladimir Sementsov-Ogievskiy
2018-10-08 19:54   ` Max Reitz
2018-10-10 12:25     ` Vladimir Sementsov-Ogievskiy
2018-08-17 12:22 ` [Qemu-devel] [PATCH v2 6/7] block/qcow2-refcount: fix out-of-file L1 entries to be zero Vladimir Sementsov-Ogievskiy
2018-10-08 20:09   ` Max Reitz [this message]
2018-08-17 12:22 ` [Qemu-devel] [PATCH v2 7/7] block/qcow2-refcount: fix out-of-file L2 entries to be read-as-zero Vladimir Sementsov-Ogievskiy
2018-10-08 20:51   ` Max Reitz
2018-10-08 22:02     ` Vladimir Sementsov-Ogievskiy
2018-10-08 22:08       ` Max Reitz
2018-10-08 22:14         ` Vladimir Sementsov-Ogievskiy
2018-10-08 22:21           ` Max Reitz
2018-10-08 23:14             ` Vladimir Sementsov-Ogievskiy
2018-10-13 12:51               ` Max Reitz
2018-10-10 16:39   ` Vladimir Sementsov-Ogievskiy
2018-10-10 16:55     ` Vladimir Sementsov-Ogievskiy
2018-10-10 16:59       ` Vladimir Sementsov-Ogievskiy
2018-10-13 12:58         ` Max Reitz
2018-12-12  8:36           ` Vladimir Sementsov-Ogievskiy
2018-12-12 12:49             ` Max Reitz
2018-10-08 15:02 ` [Qemu-devel] [PATCH 0/7] qcow2 check improvements Vladimir Sementsov-Ogievskiy

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=c0168aed-d00f-5af7-917b-a0824c9b270f@redhat.com \
    --to=mreitz@redhat.com \
    --cc=den@openvz.org \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.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).