All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, benoit.canet@irqsave.net, famz@redhat.com,
	stefanha@redhat.com
Subject: [Qemu-devel] [PATCH for 2.1 0/2] Fix commit of oversized layer
Date: Wed, 25 Jun 2014 16:55:29 -0400	[thread overview]
Message-ID: <cover.1403729574.git.jcody@redhat.com> (raw)

This fixes a regression in block-commit; if the top image is larger than the
base image, we attempt to resize the base image.  The regression is that we
fail the image truncate operation, returning -EBUSY.

Jeff Cody (2):
  block: check for RESIZE blocker in the QMP command, not
    bdrv_truncate()
  block: add qemu-iotest for resize base during live commit

 block.c                    |  4 +--
 blockdev.c                 |  5 +++
 tests/qemu-iotests/095     | 86 ++++++++++++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/095.out | 31 +++++++++++++++++
 tests/qemu-iotests/group   |  1 +
 5 files changed, 124 insertions(+), 3 deletions(-)
 create mode 100755 tests/qemu-iotests/095
 create mode 100644 tests/qemu-iotests/095.out

-- 
1.9.3

             reply	other threads:[~2014-06-25 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 20:55 Jeff Cody [this message]
2014-06-25 20:55 ` [Qemu-devel] [PATCH for 2.1 1/2] block: check for RESIZE blocker in the QMP command, not bdrv_truncate() Jeff Cody
2014-06-25 20:55 ` [Qemu-devel] [PATCH for 2.1 2/2] block: add qemu-iotest for resize base during live commit Jeff Cody
2014-06-25 22:08 ` [Qemu-devel] [PATCH for 2.1 0/2] Fix commit of oversized layer Eric Blake
2014-06-27  9:44 ` Kevin Wolf
2014-07-10  8:42   ` Fam Zheng
2014-07-10  9:25     ` Kevin Wolf
2014-07-10  9:48       ` Fam Zheng

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.1403729574.git.jcody@redhat.com \
    --to=jcody@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.