All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/2] qcow2: improve error handling when luks creation fails
Date: Tue, 19 Feb 2019 12:50:42 +0000	[thread overview]
Message-ID: <20190219125044.5416-1-berrange@redhat.com> (raw)

If qemu is built without crypto support luks creation will fail. The 188
iotest however still carried on using the partially created file. This
showed a few flaws in error handling, one during creation and one during
opening of the image.

Daniel P. Berrangé (2):
  qcow2: fail if encryption opts are provided to non-encrypted image
  qcow2: mark image as corrupt if failing during create

 block/qcow2.c | 9 +++++++++
 1 file changed, 9 insertions(+)

-- 
2.20.1

             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 Daniel P. Berrangé [this message]
2019-02-19 12:50 ` [Qemu-devel] [PATCH 1/2] qcow2: fail if encryption opts are provided to non-encrypted image Daniel P. Berrangé
2019-02-19 15:56   ` 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-1-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 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.