From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, rjones@redhat.com, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH for-1.5 0/3] qcow2: Catch some L1 table index overflows
Date: Mon, 13 May 2013 15:42:53 +0200 [thread overview]
Message-ID: <1368452576-32262-1-git-send-email-kwolf@redhat.com> (raw)
Suggestions for a better test case are welcome. But now that creating a large
image file fails, and if you somehow manage to create it anyway (qcow2.py)
opening it fails, it's hard to test the actual read/write cases.
Kevin Wolf (3):
qcow2: Catch some L1 table index overflows
qcow2.py: Subcommand for changing header fields
qemu-iotests: Try creating huge qcow2 image
block/qcow2-cluster.c | 23 ++++++++++++------
block/qcow2.c | 13 ++++++++--
block/qcow2.h | 5 ++--
tests/qemu-iotests/054 | 58 ++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/054.out | 10 ++++++++
tests/qemu-iotests/common.rc | 2 +-
tests/qemu-iotests/group | 1 +
tests/qemu-iotests/qcow2.py | 12 +++++++++
8 files changed, 111 insertions(+), 13 deletions(-)
create mode 100755 tests/qemu-iotests/054
create mode 100644 tests/qemu-iotests/054.out
--
1.8.1.4
next reply other threads:[~2013-05-13 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 13:42 Kevin Wolf [this message]
2013-05-13 13:42 ` [Qemu-devel] [PATCH for-1.5 1/3] qcow2: Catch some L1 table index overflows Kevin Wolf
2013-05-13 13:42 ` [Qemu-devel] [PATCH 2/3] qcow2.py: Subcommand for changing header fields Kevin Wolf
2013-05-13 14:59 ` Stefan Hajnoczi
2013-05-13 13:42 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: Try creating huge qcow2 image Kevin Wolf
2013-05-13 14:39 ` [Qemu-devel] [PATCH for-1.5 0/3] qcow2: Catch some L1 table index overflows Richard W.M. Jones
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=1368452576-32262-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--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).