From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/2] vmdk: Fix error for JSON descriptor file names
Date: Wed, 3 Dec 2014 14:57:21 +0100 [thread overview]
Message-ID: <1417615043-26174-1-git-send-email-mreitz@redhat.com> (raw)
This series improves the error message emitted when a vmdk file has a
JSON file name and the vmdk driver tries to read the extent files (which
will not work), and adds an appropriate test case.
v2:
- Patch 1: Only error out if the extent file name is not absolute
[Kevin]
- Patch 2: Because I changed the error message in patch 1, the test
output needs to be amended accordingly
git-backport-diff against v1:
Key:
[----] : patches are identical
[####] : number of functional differences between upstream/downstream patch
[down] : patch is downstream-only
The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
001/2:[0018] [FC] 'vmdk: Fix error for JSON descriptor file names'
002/2:[0002] [FC] 'iotests: Add test for vmdk JSON file names'
Max Reitz (2):
vmdk: Fix error for JSON descriptor file names
iotests: Add test for vmdk JSON file names
block.c | 2 +-
block/vmdk.c | 10 +++++++++-
include/block/block.h | 1 +
tests/qemu-iotests/059 | 6 ++++++
tests/qemu-iotests/059.out | 4 ++++
5 files changed, 21 insertions(+), 2 deletions(-)
--
1.9.3
next reply other threads:[~2014-12-03 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 13:57 Max Reitz [this message]
2014-12-03 13:57 ` [Qemu-devel] [PATCH v2 1/2] vmdk: Fix error for JSON descriptor file names Max Reitz
2014-12-04 1:08 ` Fam Zheng
2014-12-03 13:57 ` [Qemu-devel] [PATCH v2 2/2] iotests: Add test for vmdk JSON " Max Reitz
2014-12-04 1:09 ` Fam Zheng
2014-12-12 13:15 ` [Qemu-devel] [PATCH v2 0/2] vmdk: Fix error for JSON descriptor " 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=1417615043-26174-1-git-send-email-mreitz@redhat.com \
--to=mreitz@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).