All of lore.kernel.org
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-3.1 v3 0/2] block: Fix crash on migration with explicit child nodes
Date: Mon, 26 Nov 2018 17:17:58 +0100	[thread overview]
Message-ID: <3fed5e03-7240-3c91-84b5-107b6ada1f88@redhat.com> (raw)
In-Reply-To: <20181126160513.26369-1-kwolf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

On 26.11.18 17:05, Kevin Wolf wrote:
> v3:
> - Checking whether there are still active parents only really works with
>   a single pass, so that's what we do now [Max]
> - Test case polishing [Max]
> 
> v2:
> - Cover children that were created after their parents [Max]
> 
> Kevin Wolf (2):
>   block: Don't inactivate children before parents
>   iotests: Test migration with -blockdev
> 
>  block.c                    |  84 +++++++++++++++----------
>  tests/qemu-iotests/234     | 121 +++++++++++++++++++++++++++++++++++++
>  tests/qemu-iotests/234.out |  30 +++++++++
>  tests/qemu-iotests/group   |   1 +
>  4 files changed, 205 insertions(+), 31 deletions(-)
>  create mode 100755 tests/qemu-iotests/234
>  create mode 100644 tests/qemu-iotests/234.out

Reviewed-by: Max Reitz <mreitz@redhat.com>


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2018-11-26 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 16:05 [Qemu-devel] [PATCH for-3.1 v3 0/2] block: Fix crash on migration with explicit child nodes Kevin Wolf
2018-11-26 16:05 ` [Qemu-devel] [PATCH for-3.1 v3 1/2] block: Don't inactivate children before parents Kevin Wolf
2018-11-26 16:05 ` [Qemu-devel] [PATCH for-3.1 v3 2/2] iotests: Test migration with -blockdev Kevin Wolf
2018-11-26 16:17 ` Max Reitz [this message]

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=3fed5e03-7240-3c91-84b5-107b6ada1f88@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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.