qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, aik@ozlabs.ru,
	mreitz@redhat.com, den@openvz.org, stefanha@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] Don't write headers if BDS is INACTIVE
Date: Fri, 27 Oct 2017 04:57:52 -0400	[thread overview]
Message-ID: <cover.1509094209.git.jcody@redhat.com> (raw)

VHDX and Parallels both blindly write headers to the image file
if the images are opened R/W.  This causes an assert if the QEMU run
state is INMIGRATE.  Rather than blindly write on open, latch the first
write to the image, and update the header then.

Jeff Cody (4):
  block/vhdx.c: Don't blindly update the header
  block/parallels: code movement
  block/parallels: Don't update header until the first actual write
  qemu-iotests: update unsupported image formats in 194

 block/parallels.c      | 49 ++++++++++++++++++++++++++++++++-----------------
 block/vhdx.c           |  7 -------
 tests/qemu-iotests/194 |  2 +-
 3 files changed, 33 insertions(+), 25 deletions(-)

-- 
2.13.6

             reply	other threads:[~2017-10-27  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  8:57 Jeff Cody [this message]
2017-10-27  8:57 ` [Qemu-devel] [PATCH 1/4] block/vhdx.c: Don't blindly update the header Jeff Cody
2017-10-27  8:57 ` [Qemu-devel] [PATCH 2/4] block/parallels: code movement Jeff Cody
2017-10-27  8:57 ` [Qemu-devel] [PATCH 3/4] block/parallels: Don't update header until the first actual write Jeff Cody
2017-10-27  9:09   ` Kevin Wolf
2017-10-27 10:18     ` Jeff Cody
2017-10-29  8:59       ` Kevin Wolf
2017-10-27 12:13   ` Denis V. Lunev
2017-10-27  8:57 ` [Qemu-devel] [PATCH 4/4] qemu-iotests: update unsupported image formats in 194 Jeff Cody

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=cover.1509094209.git.jcody@redhat.com \
    --to=jcody@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=den@openvz.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).