From: "Ján Tomko" <jtomko@redhat.com>
To: Peter Krempa <pkrempa@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, libvir-list@redhat.com,
qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH v2 1/3] iotests: Specify explicit backing format where sensible
Date: Thu, 27 Feb 2020 10:03:23 +0100 [thread overview]
Message-ID: <20200227090323.GC2262365@lpt> (raw)
In-Reply-To: <20200227072046.GC20737@andariel.pipo.sk>
[-- Attachment #1: Type: text/plain, Size: 2427 bytes --]
On a Thursday in 2020, Peter Krempa wrote:
>On Wed, Feb 26, 2020 at 20:39:26 -0600, Eric Blake wrote:
>> There are many existing qcow2 images that specify a backing file but
>> no format. This has been the source of CVEs in the past, but has
>> become more prominent of a problem now that libvirt has switched to
>> -blockdev. With older -drive, at least the probing was always done by
>> qemu (so the only risk of a changed format between successive boots of
>> a guest was if qemu was upgraded and probed differently). But with
>> newer -blockdev, libvirt must specify a format; if libvirt guesses raw
>> where the image was formatted, this results in data corruption visible
>> to the guest; conversely, if libvirt guesses qcow2 where qemu was
>> using raw, this can result in potential security holes, so modern
>> libvirt instead refuses to use images without explicit backing format.
>>
>> The change in libvirt to reject images without explicit backing format
>> has pointed out that a number of tools have been far too reliant on
>> probing in the past. It's time to set a better example in our own
>> iotests of properly setting this parameter.
>>
>> iotest calls to create, rebase, convert, and amend are all impacted to
>> some degree. It's a bit annoying that we are inconsistent on command
>> line - while all of those accept -o backing_file=...,backing_fmt=...,
>> the shortcuts are different: create and rebase have -b and -F, convert
>> has -B but no -F, and amend has no shortcuts.
>>
>> Signed-off-by: Eric Blake <eblake@redhat.com>
>> ---
>
>[...]
>
>> 113 files changed, 414 insertions(+), 338 deletions(-)
>>
>> diff --git a/tests/qemu-iotests/017 b/tests/qemu-iotests/017
>> index 0a4b854e6520..585512bb296b 100755
>> --- a/tests/qemu-iotests/017
>> +++ b/tests/qemu-iotests/017
>> @@ -66,7 +66,7 @@ echo "Creating test image with backing file"
>> echo
>>
>> TEST_IMG=$TEST_IMG_SAVE
>> -_make_test_img -b "$TEST_IMG.base" 6G
>> +_make_test_img -b "$TEST_IMG.base" -F $IMGFMT 6G
>>
>
>My understanding of the intricacies of the qemu-iotest suite is not good
>enoug to be able to review this patch. Specifically $IMGFMT in this
>instance is also used in the '-f' switch of qemu-img in _make_test_img
>and I don't know if it's expected for the backing file to share the
>format.
IMGFMT is also used for the earlier creation of the base image and
I did not see it changing in any of the tests.
Jano
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-27 9:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 2:39 [PATCH v2 0/3] Tighten qemu-img rules on missing backing format Eric Blake
2020-02-27 2:39 ` [PATCH v2 1/3] iotests: Specify explicit backing format where sensible Eric Blake
2020-02-27 7:20 ` Peter Krempa
2020-02-27 9:03 ` Ján Tomko [this message]
2020-02-27 13:05 ` Eric Blake
2020-02-27 9:19 ` Ján Tomko
2020-02-27 13:08 ` Eric Blake
2020-03-05 22:58 ` Eric Blake
2020-02-27 2:39 ` [PATCH v2 2/3] block: Add support to warn on backing file change without format Eric Blake
2020-02-27 7:10 ` Peter Krempa
2020-02-27 9:22 ` Ján Tomko
2020-02-27 2:39 ` [PATCH v2 3/3] qemu-img: Deprecate use of -b without -F Eric Blake
2020-02-27 7:09 ` Peter Krempa
2020-02-27 13:13 ` Eric Blake
2020-02-27 9:43 ` Ján Tomko
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=20200227090323.GC2262365@lpt \
--to=jtomko@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@redhat.com \
--cc=pkrempa@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).