qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	"R . Nageswara Sastry" <nasastry@in.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] Misc qcow2 corruption checks
Date: Thu, 2 Nov 2017 18:24:40 +0100	[thread overview]
Message-ID: <5d18fa25-bde1-31a6-568e-3d224c5bbe8b@redhat.com> (raw)
In-Reply-To: <cover.1509550787.git.berto@igalia.com>

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

On 2017-11-01 16:42, Alberto Garcia wrote:
> Misc qcow2 corruption checks
> 
> This series contains a few checks that prevent QEMU from crashing
> under some scenarios with corrupted qcow2 images.
> 
> The first patch solves the crash reported here:
> 
>   https://bugs.launchpad.net/qemu/+bug/1728615
> 
> And the others solve similar crashes that I detected in the process of
> fixing this one.
> 
> Regards,
> 
> Berto

There are two more cases which might need a check that the return value
of an allocation function isn't 0:

The first is qcow2_alloc_bytes() which has an assert(offset) after
potentially setting offset = new_cluster (with new_cluster being the
return value of alloc_clusters_noref()).

The second is qcow2_crypto_hdr_init_func() which is simply missing a
pre-write overlap check.

The rest (besides L2 table and refblock allocation) should be guarded by
the pre-write overlap check.

Do you want to fix these or do we need another volunteer? :-)

Max


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

  parent reply	other threads:[~2017-11-02 17:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 15:42 [Qemu-devel] [PATCH 0/4] Misc qcow2 corruption checks Alberto Garcia
2017-11-01 15:42 ` [Qemu-devel] [PATCH 1/4] qcow2: Prevent allocating refcount blocks at offset 0 Alberto Garcia
2017-11-02 17:28   ` Max Reitz
2017-11-03  9:04     ` Alberto Garcia
2017-11-01 15:42 ` [Qemu-devel] [PATCH 2/4] qcow2: Prevent allocating L2 tables " Alberto Garcia
2017-11-02 17:31   ` Max Reitz
2017-11-03  9:56     ` Alberto Garcia
2017-11-01 15:42 ` [Qemu-devel] [PATCH 3/4] qcow2: Don't open images with header.refcount_table_clusters == 0 Alberto Garcia
2017-11-02 17:41   ` Max Reitz
2017-11-01 15:42 ` [Qemu-devel] [PATCH 4/4] qcow2: Add iotest for an empty refcount table Alberto Garcia
2017-11-02 17:43   ` Max Reitz
2017-11-02 17:24 ` Max Reitz [this message]
2017-11-03 12:32   ` [Qemu-devel] [PATCH 0/4] Misc qcow2 corruption checks Alberto Garcia

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=5d18fa25-bde1-31a6-568e-3d224c5bbe8b@redhat.com \
    --to=mreitz@redhat.com \
    --cc=berto@igalia.com \
    --cc=kwolf@redhat.com \
    --cc=nasastry@in.ibm.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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 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).