qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Levitsky <mlevitsk@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Eric Blake" <eblake@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH] tests: fix I/O test for hosts defaulting to LUKSv2
Date: Sun, 29 Sep 2019 21:32:25 +0300	[thread overview]
Message-ID: <b80eaa54fba414c26f329b1021aae1b231ba77a6.camel@redhat.com> (raw)
In-Reply-To: <20190927165153.GO20911@redhat.com>

On Fri, 2019-09-27 at 17:51 +0100, Daniel P. Berrangé wrote:
> On Fri, Sep 27, 2019 at 10:26:27AM -0500, Eric Blake wrote:
> > On 9/27/19 5:11 AM, Daniel P. Berrangé wrote:
> > > Some distros are now defaulting to LUKS version 2 which QEMU cannot
> > > process. For our I/O test that validates interoperability between the
> > > kernel/cryptsetup and QEMU, we need to explicitly ask for version 1
> > > of the LUKS format.
> > > 
> > 
> > Ultimately, it would be nice to get LUKS 2 support in qemu too, but that's a
> > much bigger job.  This is fine for now.
If there is need, I volunteer to research the area and if this is feasible,
add support for LUKSv2.
I haven't yet had looked at the spec.

Best regards,
	Maxim Levitsky



  reply	other threads:[~2019-09-29 18:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 10:11 [PATCH] tests: fix I/O test for hosts defaulting to LUKSv2 Daniel P. Berrangé
2019-09-27 15:26 ` Eric Blake
2019-09-27 16:35   ` Maxim Levitsky
2019-09-27 16:51   ` Daniel P. Berrangé
2019-09-29 18:32     ` Maxim Levitsky [this message]
2019-10-07 11:23 ` Max Reitz

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=b80eaa54fba414c26f329b1021aae1b231ba77a6.camel@redhat.com \
    --to=mlevitsk@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@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).