From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH for-3.1 v2 0/2] block: Fix crash on migration with explicit child nodes
Date: Mon, 26 Nov 2018 15:16:37 +0100 [thread overview]
Message-ID: <20181126141639.13208-1-kwolf@redhat.com> (raw)
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 | 32 ++++++++++-
tests/qemu-iotests/234 | 115 +++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/234.out | 27 +++++++++
tests/qemu-iotests/group | 1 +
4 files changed, 174 insertions(+), 1 deletion(-)
create mode 100755 tests/qemu-iotests/234
create mode 100644 tests/qemu-iotests/234.out
--
2.19.1
next reply other threads:[~2018-11-26 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 14:16 Kevin Wolf [this message]
2018-11-26 14:16 ` [Qemu-devel] [PATCH for-3.1 v2 1/2] block: Don't inactivate children before parents Kevin Wolf
2018-11-26 14:34 ` Max Reitz
2018-11-26 14:16 ` [Qemu-devel] [PATCH for-3.1 v2 2/2] iotests: Test migration with -blockdev Kevin Wolf
2018-11-26 14:37 ` 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=20181126141639.13208-1-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@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 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).