From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Khoa Huynh <khoa@us.ibm.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 7/7] qemu-iotests: add 039 qcow2 lazy refcounts test
Date: Wed, 25 Jul 2012 11:54:50 -0600 [thread overview]
Message-ID: <501032EA.8050307@redhat.com> (raw)
In-Reply-To: <1343218884-14980-8-git-send-email-stefanha@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On 07/25/2012 06:21 AM, Stefan Hajnoczi wrote:
> This tests establishes the basic post-conditions of the qcow2 lazy
> refcounts features:
>
> 1. If the image was closed normally, it is marked clean.
>
> 2. If an allocating write was performed and the image was not close
> normally, then it is marked dirty.
>
> a. Written data can be read back successfully.
> b. The image file can be repaired and will be marked clean again.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> +++ b/tests/qemu-iotests/039
> @@ -0,0 +1,117 @@
> +#!/bin/bash
Since you are assuming bash (and even if you were to assume POSIX
/bin/sh)...
> +
> +seq=`basename $0`
I prefer $() over ``.
> +echo "QA output created by $seq"
> +
> +here=`pwd`
POSIX (and therefore bash) guarantees that $PWD is sane, and faster to
access than $(pwd).
> +tmp=/tmp/$$
That's not very secure. It may be worth using bash's $RANDOM, or using
mkstemp(1).
Beyond that, the series seemed reasonable to me.
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2012-07-25 17:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 12:21 [Qemu-devel] [PATCH v2 0/7] qcow2: implement lazy refcounts optimization Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 1/7] docs: add dirty bit to qcow2 specification Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 2/7] qcow2: introduce dirty bit Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 3/7] docs: add lazy refcounts bit to qcow2 specification Stefan Hajnoczi
2012-07-26 12:57 ` Kevin Wolf
2012-07-26 15:36 ` Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 4/7] qemu-iotests: ignore qemu-img create lazy_refcounts output Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 5/7] qcow2: implement lazy refcounts Stefan Hajnoczi
2012-07-26 13:15 ` Kevin Wolf
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 6/7] qemu-io: add "abort" command to simulate program crash Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 7/7] qemu-iotests: add 039 qcow2 lazy refcounts test Stefan Hajnoczi
2012-07-25 17:54 ` Eric Blake [this message]
2012-07-25 22:45 ` Stefan Hajnoczi
2012-07-25 23:41 ` Eric Blake
2012-07-26 13:28 ` Kevin Wolf
2012-07-27 7:56 ` Stefan Hajnoczi
2012-07-27 8:07 ` Kevin Wolf
2012-07-30 10:09 ` Stefan Hajnoczi
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=501032EA.8050307@redhat.com \
--to=eblake@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=khoa@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).