From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>, Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] Improve I/O tests coverage of LUKS
Date: Thu, 9 Feb 2017 14:42:53 +0000 [thread overview]
Message-ID: <20170209144253.GA26192@redhat.com> (raw)
In-Reply-To: <20170124115748.21473-1-berrange@redhat.com>
ping ?
On Tue, Jan 24, 2017 at 11:57:43AM +0000, Daniel P. Berrange wrote:
> The main goal of this series is to get the I/O tests passing
> 100% with LUKS when run with './check -luks'. It also adds a
> few more combinations to the LUKS/dmcrypt interoperability
> test.
>
> To make LUKS testing not quite as slow, we drop the PBKDF
> iteration count down to a very small value. This doesn't
> remove all overhead, as formatting the volume will always
> measure PBKDF timing over a 1 second interval.
>
> Changed in v3:
>
> - Fix some typos in commit message(s) (Eric)
>
> Changed in v2:
>
> - Split off patch that change check.time recording since
> it was not a direct dependancy
> - Skip new 159 & 170 tests which don't work due to qemu-img
> dd limitations
>
> Daniel P. Berrange (5):
> iotests: skip 159 & 170 with luks format
> iotests: fix remainining tests to work with LUKS
> iotests: reduce PBKDF iterations when testing LUKS
> iotests: add more LUKS hash combination tests
> iotests: chown LUKS device before qemu-io launches
>
> tests/qemu-iotests/033 | 16 +-
> tests/qemu-iotests/120 | 25 +-
> tests/qemu-iotests/140 | 15 +-
> tests/qemu-iotests/145 | 18 +-
> tests/qemu-iotests/149 | 26 +-
> tests/qemu-iotests/149.out | 1002 ++++++++++++++++++++++++++++----------
> tests/qemu-iotests/157 | 17 +-
> tests/qemu-iotests/157.out | 16 +-
> tests/qemu-iotests/159 | 2 +-
> tests/qemu-iotests/170 | 2 +-
> tests/qemu-iotests/common.filter | 3 +-
> tests/qemu-iotests/common.rc | 3 +
> 12 files changed, 847 insertions(+), 298 deletions(-)
>
> --
> 2.9.3
>
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
prev parent reply other threads:[~2017-02-09 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 11:57 [Qemu-devel] [PATCH v3 0/5] Improve I/O tests coverage of LUKS Daniel P. Berrange
2017-01-24 11:57 ` [Qemu-devel] [PATCH v3 1/5] iotests: skip 159 & 170 with luks format Daniel P. Berrange
2017-02-12 0:06 ` Max Reitz
2017-01-24 11:57 ` [Qemu-devel] [PATCH v3 2/5] iotests: fix remainining tests to work with LUKS Daniel P. Berrange
2017-02-12 0:50 ` Max Reitz
2017-01-24 11:57 ` [Qemu-devel] [PATCH v3 3/5] iotests: reduce PBKDF iterations when testing LUKS Daniel P. Berrange
2017-01-24 11:57 ` [Qemu-devel] [PATCH v3 4/5] iotests: add more LUKS hash combination tests Daniel P. Berrange
2017-01-24 11:57 ` [Qemu-devel] [PATCH v3 5/5] iotests: chown LUKS device before qemu-io launches Daniel P. Berrange
2017-02-09 14:42 ` Daniel P. Berrange [this message]
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=20170209144253.GA26192@redhat.com \
--to=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).