From: Eric Blake <eblake@redhat.com>
To: Bug 1711602 <1711602@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1711602] Re: --copy-storage-all failing with qemu 2.10
Date: Wed, 23 Aug 2017 10:13:59 -0500 [thread overview]
Message-ID: <d299b9c5-c380-4420-06b5-80dea66b0688@redhat.com> (raw)
In-Reply-To: <150350012253.19046.4268047906681155989.malone@chaenomeles.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On 08/23/2017 09:55 AM, ChristianEhrhardt wrote:
> Ok, clarified with Stefanha
> It has exactly the same title as a series of 18th August which was related to a similar issue.
> It is about an hour old now on qemu-devel, quoting
>
> "This fixes the issue reported as
> https://bugs.launchpad.net/bugs/1711602
>
> Fam Zheng (3):
> block-backend: Refactor inactivate check
> block-backend: Allow more "can inactivate" cases
> mirror: Mark target BB as "force allow inactivate"
>
> Stefan Hajnoczi (1):
> block: Update open_flags after ->inactivate() callback"
>
>
> I'll prep a build with that and test as well
Here's what is brewing for my pull request, although if you can
successfully test things, I'm happy to add a Tested-by: tag before
actually sending the pull request:
git fetch git://repo.or.cz/qemu/ericb.git nbd
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-23 15:14 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <150305905460.11582.12289718300820278863.malonedeb@wampee.canonical.com>
2017-08-18 14:15 ` [Qemu-devel] [Bug 1711602] Re: --copy-storage-all failing with qemu 2.10 ChristianEhrhardt
2017-08-18 14:22 ` ChristianEhrhardt
2017-08-18 15:03 ` ChristianEhrhardt
2017-08-18 15:03 ` ChristianEhrhardt
2017-08-18 15:04 ` ChristianEhrhardt
2017-08-18 15:04 ` ChristianEhrhardt
2017-08-18 15:06 ` ChristianEhrhardt
2017-08-18 15:09 ` ChristianEhrhardt
2017-08-18 17:56 ` Dr. David Alan Gilbert
2017-08-21 14:55 ` ChristianEhrhardt
2017-08-21 14:55 ` ChristianEhrhardt
2017-08-21 14:55 ` ChristianEhrhardt
2017-08-21 14:56 ` ChristianEhrhardt
2017-08-21 15:46 ` Dr. David Alan Gilbert
2017-08-22 8:51 ` ChristianEhrhardt
2017-08-22 8:54 ` ChristianEhrhardt
2017-08-22 8:58 ` ChristianEhrhardt
2017-08-22 9:01 ` ChristianEhrhardt
2017-08-22 9:08 ` ChristianEhrhardt
2017-08-22 9:26 ` Dr. David Alan Gilbert
2017-08-22 9:51 ` Dr. David Alan Gilbert
2017-08-22 10:20 ` ChristianEhrhardt
2017-08-22 10:57 ` Dr. David Alan Gilbert
2017-08-22 11:13 ` Dr. David Alan Gilbert
2017-08-22 11:14 ` ChristianEhrhardt
2017-08-22 11:18 ` ChristianEhrhardt
2017-08-22 11:23 ` Dr. David Alan Gilbert
2017-08-22 11:33 ` ChristianEhrhardt
2017-08-22 11:44 ` Dr. David Alan Gilbert
2017-08-22 11:46 ` Dr. David Alan Gilbert
2017-08-22 11:50 ` ChristianEhrhardt
2017-08-22 15:05 ` Dr. David Alan Gilbert
2017-08-22 15:47 ` ChristianEhrhardt
2017-08-22 17:57 ` ChristianEhrhardt
2017-08-22 19:21 ` ChristianEhrhardt
2017-08-23 8:02 ` Dr. David Alan Gilbert
2017-08-23 14:14 ` Stefan Hajnoczi
2017-08-23 14:41 ` Dr. David Alan Gilbert
2017-08-23 14:46 ` ChristianEhrhardt
2017-08-23 14:55 ` ChristianEhrhardt
2017-08-23 15:13 ` Eric Blake [this message]
2017-08-23 16:56 ` ChristianEhrhardt
2017-08-23 17:01 ` ChristianEhrhardt
2017-08-23 18:10 ` Dr. David Alan Gilbert
2017-08-23 18:55 ` Dr. David Alan Gilbert
2017-08-23 19:06 ` Dr. David Alan Gilbert
2017-08-23 19:10 ` ChristianEhrhardt
2017-08-23 21:02 ` ChristianEhrhardt
2017-09-02 8:04 ` Launchpad Bug Tracker
2017-12-15 16:10 ` Thomas Huth
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=d299b9c5-c380-4420-06b5-80dea66b0688@redhat.com \
--to=eblake@redhat.com \
--cc=1711602@bugs.launchpad.net \
--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).