From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com
Subject: [Qemu-devel] [PATCH 0/6] block: Add flush after metadata writes
Date: Fri, 18 Jun 2010 17:03:23 +0200 [thread overview]
Message-ID: <1276873409-8235-1-git-send-email-kwolf@redhat.com> (raw)
This addresses the data integrity problems which are described for qcow at
http://wiki.qemu.org/Features/Qcow2DataIntegrity#Metadata_update_ordering.2C_Part_2
These problems are the same for all writable image formats, so this series
contains a patch for each of them.
The only exception is VDI which uses AIO for writing its metadata. It needs
a different fix.
Kevin Wolf (6):
block: Add bdrv_(p)write_sync
cow: Use bdrv_(p)write_sync for metadata writes
qcow: Use bdrv_(p)write_sync for metadata writes
qcow2: Use bdrv_(p)write_sync for metadata writes
vmdk: Use bdrv_(p)write_sync for metadata writes
vpc: Use bdrv_(p)write_sync for metadata writes
block.c | 37 +++++++++++++++++++++++++++++++++++++
block.h | 4 ++++
block/cow.c | 20 +++++++++++---------
block/qcow.c | 18 ++++++++++--------
block/qcow2-cluster.c | 24 ++++++++++++------------
block/qcow2-refcount.c | 24 ++++++++++++------------
block/qcow2-snapshot.c | 23 +++++++++++------------
block/qcow2.c | 10 +++++-----
block/vmdk.c | 10 +++++-----
block/vpc.c | 9 +++++----
10 files changed, 112 insertions(+), 67 deletions(-)
next reply other threads:[~2010-06-18 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 15:03 Kevin Wolf [this message]
2010-06-18 15:03 ` [Qemu-devel] [PATCH 1/6] block: Add bdrv_(p)write_sync Kevin Wolf
2010-06-18 15:03 ` [Qemu-devel] [PATCH 2/6] cow: Use bdrv_(p)write_sync for metadata writes Kevin Wolf
2010-06-18 15:03 ` [Qemu-devel] [PATCH 3/6] qcow: " Kevin Wolf
2010-06-18 15:03 ` [Qemu-devel] [PATCH 4/6] qcow2: " Kevin Wolf
2010-06-18 15:03 ` [Qemu-devel] [PATCH 5/6] vmdk: " Kevin Wolf
2010-06-18 15:03 ` [Qemu-devel] [PATCH 6/6] vpc: " Kevin Wolf
2010-06-20 7:46 ` [Qemu-devel] [PATCH 0/6] block: Add flush after " 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=1276873409-8235-1-git-send-email-kwolf@redhat.com \
--to=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).