From: Jeff Cody <jcody@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, stefanha@redhat.com, benoit@irqsave.net
Subject: Re: [Qemu-devel] [PATCH v2 4/5] block: qemu-iotests - fix image cleanup when using spaced pathnames
Date: Thu, 10 Apr 2014 14:09:51 -0400 [thread overview]
Message-ID: <20140410180951.GE4859@localhost.localdomain> (raw)
In-Reply-To: <5346AF2A.3050701@redhat.com>
On Thu, Apr 10, 2014 at 08:48:10AM -0600, Eric Blake wrote:
> On 04/10/2014 08:43 AM, Eric Blake wrote:
> > On 04/10/2014 06:53 AM, Jeff Cody wrote:
> >
> >>>> +++ b/tests/qemu-iotests/common.rc
> >>>> @@ -178,10 +178,10 @@ _rm_test_img()
> >>>> local img=$1
> >>>
> >>> Since we are quoting $img, should we quote $1 as well?
> >>>
>
> >
> > http://austingroupbugs.net/view.php?id=351
> >
> > But even with the notion of an assignment-context argument added to a
> > future version of POSIX, the reality is that given the present standard,
> > it's safer to either use "" to ensure no word splitting:
>
> Well, if you were trying to be portable to multiple shells, then it
> would matter. But as this script is explicitly being run under
> /bin/bash, and as bash already has support for declaration utilities
> where local is one such utility, your script as written is safe without
> "" in the arguments to local. So I'm fine whether you choose to change
> it in a respin or to leave it as written in this version.
>
Hi Eric,
Thanks - I consulted specifically with just the bash documentation, so
you are right, this script (and likely most of qemu-iotests) is
bash-only.
That particular line is context as well, and not an actual change - so
while it may be a good idea to quote it to make the scripts closer to
posix-only, my guess is there are quite a few similar lines throughout
all the qemu-iotests scripts.
Given that, if we address that it would probably make sense to do that
in a bash->posix conversion series for all the scripts (likely a low
priority, however).
Jeff
next prev parent reply other threads:[~2014-04-10 18:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 2:41 [Qemu-devel] [PATCH v2 0/5] Add common QEMU control functionality to qemu-iotests Jeff Cody
2014-04-10 2:41 ` [Qemu-devel] [PATCH v2 1/5] block: qemu-iotests - add common.qemu, for bash-controlled qemu tests Jeff Cody
2014-04-10 5:27 ` Fam Zheng
2014-04-10 19:07 ` Jeff Cody
2014-04-10 2:41 ` [Qemu-devel] [PATCH v2 2/5] block: qemu-iotests - update 085 to use common.qemu Jeff Cody
2014-04-10 6:10 ` Fam Zheng
2014-04-10 19:28 ` Jeff Cody
2014-04-10 2:41 ` [Qemu-devel] [PATCH v2 3/5] block: qemu-iotests - test for live migration Jeff Cody
2014-04-10 6:16 ` Fam Zheng
2014-04-10 11:10 ` Jeff Cody
2014-04-10 2:41 ` [Qemu-devel] [PATCH v2 4/5] block: qemu-iotests - fix image cleanup when using spaced pathnames Jeff Cody
2014-04-10 7:53 ` Fam Zheng
2014-04-10 12:53 ` Jeff Cody
2014-04-10 14:43 ` Eric Blake
2014-04-10 14:48 ` Eric Blake
2014-04-10 18:09 ` Jeff Cody [this message]
2014-04-11 0:59 ` Fam Zheng
2014-04-10 2:41 ` [Qemu-devel] [PATCH v2 5/5] block: qemu-iotests: make test 019 and 086 work with " Jeff Cody
2014-04-10 7:51 ` Fam Zheng
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=20140410180951.GE4859@localhost.localdomain \
--to=jcody@redhat.com \
--cc=benoit@irqsave.net \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).