All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-stable@nongnu.org, qemu-devel@nongnu.org,
	stefanha@redhat.com, mreitz@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] Active commit regression fix
Date: Mon,  1 Feb 2016 20:33:09 -0500	[thread overview]
Message-ID: <cover.1454376655.git.jcody@redhat.com> (raw)

Changes from v1:

* Rather than allow insertion when bs->device_listtqe_prev points to
  a NULL entry, make sure than we follow the block scheme of enforcing
  bs->device_list->tqe_prev is NULL upon deletion. (Thanks Max!)

Bug #1300209 is a regression in 2.5, introduced during the 
change away from bdrv_swap().

When we change the parent backing link (change_parent_backing_link),
we must also accomodate non-NULL tqe_prev pointers that point to a
NULL entry.  Please see patch #1 for more details.

Jeff Cody (2):
  block: set device_list.tqe_prev to NULL on BDS removal
  block: qemu-iotests - add test for snapshot, commit, snapshot bug

 block.c                    |  24 ++++++----
 blockdev.c                 |   3 +-
 include/block/block.h      |   1 +
 tests/qemu-iotests/143     | 114 +++++++++++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/143.out |  24 ++++++++++
 tests/qemu-iotests/group   |   1 +
 6 files changed, 155 insertions(+), 12 deletions(-)
 create mode 100755 tests/qemu-iotests/143
 create mode 100644 tests/qemu-iotests/143.out

-- 
1.9.3

             reply	other threads:[~2016-02-02  1:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02  1:33 Jeff Cody [this message]
2016-02-02  1:33 ` [Qemu-devel] [PATCH v2 1/2] block: set device_list.tqe_prev to NULL on BDS removal Jeff Cody
2016-02-02 17:02   ` Max Reitz
2016-02-02  1:33 ` [Qemu-devel] [PATCH v2 2/2] block: qemu-iotests - add test for snapshot, commit, snapshot bug Jeff Cody
2016-02-02 17:03   ` Max Reitz
2016-02-02 17:08 ` [Qemu-devel] [PATCH v2 0/2] Active commit regression fix Max Reitz

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.1454376655.git.jcody@redhat.com \
    --to=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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.