From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 2/5] iotests: fix remainining tests to work with LUKS
Date: Wed, 31 May 2017 18:08:47 +0200 [thread overview]
Message-ID: <651dfffa-b953-4879-06bb-2affb39bdcef@redhat.com> (raw)
In-Reply-To: <73621dcd-ace7-c7fa-8dd2-701ea7d6d249@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
On 2017-05-31 17:59, Eric Blake wrote:
> On 05/31/2017 10:33 AM, Max Reitz wrote:
>> On 2017-05-09 19:33, Daniel P. Berrange wrote:
>>> The tests 033, 140, 145 and 157 were all broken
>>> when run with LUKS, since they did not correctly use
>>> the required image opts args syntax to specify the
>>> decryption secret. Further, the 120 test simply does
>>> not make sense to run with luks, as the scenario
>>> exercised is not relevant.
>>>
>>> The test 181 was broken when run with LUKS because
>>> it didn't take account of fact that $TEST_IMG was
>>> already in image opts syntax. The launch_qemu
>>> helper also didn't register the secret object
>>> providing the LUKS password.
>
>>>
>>> +if test "$IMGOPTSSYNTAX" = "true"
>>> +then
>>> + SYSEMU_DRIVE_ARG=if=none,media=cdrom,id=drv,$TEST_IMG
>>
>> I would like to propose wrapping this (or at least $TEST_IMG) in quotes,
>
> Makes no difference in assignment context (other than consistency that
> it's an easier rule to always quote even when not necessary, than it is
> to remember which contexts don't need quoting).
>
>> but I'm aware of the fact that the whole test environment breaks if you
>> have a TEST_DIR with whitespace in it, so I don't mind...
>>
>> (But it is a bit weird to put $TEST_IMG into quotes below and then use
>> $SYSEMU_DRIVE_ARG unquoted.)
>
> Assigning to SYSEMU_DRIVE_ARG without quotes works even if TEST_IMG
> contains spaces, but expanding SYSEMU_DRIVE_ARGS without quotes indeed
> breaks (whether or not you assigned with quotes).
Interesting, thanks. (I only knew that foo=$bar worked.)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]
next prev parent reply other threads:[~2017-05-31 16:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 17:33 [Qemu-devel] [PATCH v5 0/5] Improve I/O tests coverage of LUKS Daniel P. Berrange
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 1/5] iotests: skip 159 & 170 with luks format Daniel P. Berrange
2017-05-31 15:12 ` Max Reitz
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 2/5] iotests: fix remainining tests to work with LUKS Daniel P. Berrange
2017-05-09 17:49 ` Eric Blake
2017-05-31 15:33 ` Max Reitz
2017-05-31 15:59 ` Eric Blake
2017-05-31 16:08 ` Max Reitz [this message]
2017-06-01 8:36 ` Daniel P. Berrange
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 3/5] iotests: reduce PBKDF iterations when testing LUKS Daniel P. Berrange
2017-05-31 15:41 ` Max Reitz
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 4/5] iotests: add more LUKS hash combination tests Daniel P. Berrange
2017-05-31 16:09 ` Max Reitz
2017-05-09 17:33 ` [Qemu-devel] [PATCH v5 5/5] iotests: chown LUKS device before qemu-io launches Daniel P. Berrange
2017-05-31 16:15 ` Max Reitz
2017-06-01 8:40 ` Daniel P. Berrange
2017-06-07 12:33 ` 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=651dfffa-b953-4879-06bb-2affb39bdcef@redhat.com \
--to=mreitz@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@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).