From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
jsnow@redhat.com, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/4] qemu-io: Don't die on second open
Date: Mon, 5 Jun 2017 14:58:47 -0500 [thread overview]
Message-ID: <dbe7598c-77bb-eb1c-ba0c-59ebb600ae57@redhat.com> (raw)
In-Reply-To: <20170605190824.25184-2-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]
On 06/05/2017 02:08 PM, Eric Blake wrote:
>
> Note, however, that we do have some qemu-iotests that do 'qemu-io
> -c "open file" -c "$something"'; such tests will now proceed to
> attempt $something whether or not the open succeeded, the same way
> as if the two commands had been attempted in interactive mode; but it
> also means that it is now possible to use -c close and have a single
> qemu-io command line operate on more than one file even without
> using interactive mode. Although the '-c open' action is a subtle
> change in behavior, remember that qemu-io is for debugging purposes,
> so as long as it serves the needs of qemu-iotests while still being
> reasonable for interactive use, it should not be a problem.
Bummer - iotest 60 catches me:
+++ 060.out.bad 2017-06-05 14:55:48.336814834 -0500
@@ -21,6 +21,7 @@
refcount bits: 16
corrupt: true
can't open device TEST_DIR/t.IMGFMT: IMGFMT: Image is corrupt; cannot
be opened read/write
+no file open, try 'help open'
read 512/512 bytes at offset 0
512 bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
Looks like 114 and 153 as well. I'll have to post a v4 (serves me right
for JUST testing 177).
Also, I'm seeing a segfault on 68 that exists on current master:
068 1s ... - output mismatch (see 068.out.bad)
--- /home/eblake/qemu/tests/qemu-iotests/068.out 2017-06-01
17:01:25.113094957 -0500
+++ 068.out.bad 2017-06-05 14:55:54.140835402 -0500
@@ -6,6 +6,8 @@
QEMU X.Y.Z monitor - type 'help' for more information
(qemu) savevm 0
(qemu) quit
+./common.config: line 107: 13333 Segmentation fault (core dumped)
( if [ -n "${QEMU_NEED_PID}" ]; then
+ echo $BASHPID > "${QEMU_TEST_DIR}/qemu-${_QEMU_HANDLE}.pid";
+fi; exec "$QEMU_PROG" $QEMU_OPTIONS "$@" )
QEMU X.Y.Z monitor - type 'help' for more information
-(qemu) quit
-*** done
+(qemu) *** done
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-06-05 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 19:08 [Qemu-devel] [PATCH v3 0/4] more blkdebug tweaks Eric Blake
2017-06-05 19:08 ` [Qemu-devel] [PATCH v3 1/4] qemu-io: Don't die on second open Eric Blake
2017-06-05 19:58 ` Eric Blake [this message]
2017-06-06 12:51 ` Kevin Wolf
2017-06-05 19:08 ` [Qemu-devel] [PATCH v3 2/4] block: Guarantee that *file is set on bdrv_get_block_status() Eric Blake
2017-06-05 19:08 ` [Qemu-devel] [PATCH v3 3/4] block: Simplify use of BDRV_BLOCK_RAW Eric Blake
2017-06-05 19:08 ` [Qemu-devel] [PATCH v3 4/4] blkdebug: Support .bdrv_co_get_block_status Eric Blake
2017-06-05 19:31 ` [Qemu-devel] [PATCH v3 0/4] more blkdebug tweaks no-reply
2017-06-05 19:35 ` Eric Blake
2017-06-06 12:19 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
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=dbe7598c-77bb-eb1c-ba0c-59ebb600ae57@redhat.com \
--to=eblake@redhat.com \
--cc=jsnow@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).