From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Max Reitz" <mreitz@redhat.com>,
qemu-block@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH 1/2] qcow2: fail if encryption opts are provided to non-encrypted image
Date: Tue, 19 Feb 2019 12:50:43 +0000 [thread overview]
Message-ID: <20190219125044.5416-2-berrange@redhat.com> (raw)
In-Reply-To: <20190219125044.5416-1-berrange@redhat.com>
If the qcow2 image does not have any encryption method specified in its
header, the user should not be providing any encryption options when
opening it. We already detect this if the user had set "encrypt.format"
but this field is optional so must consider any "encrypt.*" option to be
an error.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---
block/qcow2.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/block/qcow2.c b/block/qcow2.c
index 65a54c9ac6..ecc577175f 100644
--- a/block/qcow2.c
+++ b/block/qcow2.c
@@ -1045,6 +1045,12 @@ static int qcow2_update_options_prepare(BlockDriverState *bs,
ret = -EINVAL;
goto fail;
}
+ if (encryptopts && qdict_size(encryptopts)) {
+ error_setg(errp, "No encryption in image header, but encryption "
+ "options provided");
+ ret = -EINVAL;
+ goto fail;
+ }
break;
case QCOW_CRYPT_AES:
--
2.20.1
next prev parent reply other threads:[~2019-02-19 12:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 12:50 [Qemu-devel] [PATCH 0/2] qcow2: improve error handling when luks creation fails Daniel P. Berrangé
2019-02-19 12:50 ` Daniel P. Berrangé [this message]
2019-02-19 15:56 ` [Qemu-devel] [PATCH 1/2] qcow2: fail if encryption opts are provided to non-encrypted image Eric Blake
2019-02-22 19:17 ` Max Reitz
2019-02-25 10:36 ` Daniel P. Berrangé
2019-02-19 12:50 ` [Qemu-devel] [PATCH 2/2] qcow2: mark image as corrupt if failing during create Daniel P. Berrangé
2019-02-19 16:11 ` Eric Blake
2019-02-19 16:19 ` Daniel P. Berrangé
2019-02-22 19:21 ` Max Reitz
2019-02-25 10:40 ` Daniel P. Berrangé
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=20190219125044.5416-2-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).