From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@gmail.com
Subject: [Qemu-devel] [PATCH 0/2] qcow2: Rework header updates
Date: Tue, 7 Feb 2012 16:05:38 +0100 [thread overview]
Message-ID: <1328627140-9923-1-git-send-email-kwolf@redhat.com> (raw)
This series does not only fix the chance of breaking images with a crash in the
middle of a backing file link update, but also fixes header updates in images
with unknown header extensions. It provides functions to update the whole
header instead of only the header extensions.
These fixes and improvements are a prerequisite for any qcow3 code.
Kevin Wolf (2):
qcow2: Update whole header at once
qcow2: Keep unknown header extension when rewriting header
block/qcow2.c | 194 +++++++++++++++++++++++++++++++++++++++------------------
block/qcow2.h | 9 +++
2 files changed, 143 insertions(+), 60 deletions(-)
--
1.7.6.5
next reply other threads:[~2012-02-07 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 15:05 Kevin Wolf [this message]
2012-02-07 15:05 ` [Qemu-devel] [PATCH 1/2] qcow2: Update whole header at once Kevin Wolf
2012-02-07 15:05 ` [Qemu-devel] [PATCH 2/2] qcow2: Keep unknown header extension when rewriting header 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=1328627140-9923-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).