From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 0/4] qcow2: clean-ups around lazy refcounts
Date: Tue, 31 Jul 2012 16:38:17 +0100 [thread overview]
Message-ID: <1343749101-4852-1-git-send-email-stefanha@linux.vnet.ibm.com> (raw)
The qcow2 lazy refcount feature was merged with two pending clean-ups suggested
by Kevin:
1. Ensure that qemu-iotests/check -nocache 039 does not fail.
2. Fix qemu-img check output when a dirty image file is opened. It currently
omits the error summary because automatic repair cleans the image during
bdrv_open() before qemu-img.c can call bdrv_check().
Stefan Hajnoczi (4):
qed: mark image clean after repair succeeds
qcow2: mark image clean after repair succeeds
block: add BLOCK_O_CHECK for qemu-img check
qemu-iotests: skip 039 with ./check -nocache
block.h | 1 +
block/qcow2.c | 32 +++++++++++++++++---------------
block/qed-check.c | 26 ++++++++++++++++++++++++++
block/qed.c | 11 ++---------
block/qed.h | 5 +++++
qemu-img.c | 2 +-
tests/qemu-iotests/039 | 1 +
tests/qemu-iotests/039.out | 6 ++++++
tests/qemu-iotests/common.rc | 14 ++++++++++++++
9 files changed, 73 insertions(+), 25 deletions(-)
--
1.7.10.4
next reply other threads:[~2012-07-31 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 15:38 Stefan Hajnoczi [this message]
2012-07-31 15:38 ` [Qemu-devel] [PATCH 1/4] qed: mark image clean after repair succeeds Stefan Hajnoczi
2012-07-31 15:38 ` [Qemu-devel] [PATCH 2/4] qcow2: " Stefan Hajnoczi
2012-07-31 15:38 ` [Qemu-devel] [PATCH 3/4] block: add BLOCK_O_CHECK for qemu-img check Stefan Hajnoczi
2012-07-31 15:38 ` [Qemu-devel] [PATCH 4/4] qemu-iotests: skip 039 with ./check -nocache 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=1343749101-4852-1-git-send-email-stefanha@linux.vnet.ibm.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--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).