From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-block@nongnu.org
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block-backend: allow flush on devices with open tray
Date: Mon, 13 Jun 2016 13:57:27 -0400 [thread overview]
Message-ID: <1f901da0-d30d-76ef-f417-ee61d74bc421@redhat.com> (raw)
In-Reply-To: <575B4268.7080501@redhat.com>
On 06/10/2016 06:42 PM, Eric Blake wrote:
> On 06/10/2016 03:59 PM, John Snow wrote:
>> If a device still has an attached BDS because the medium has not yet
>> been removed, we will be unable to migrate to a new host because
>> blk_flush will return an error for that backend.
>>
>> Replace the call to blk_is_available to blk_is_inserted to weaken
>> the check and allow flushes from the backend to work, while still
>> disallowing flushes from the frontend/device model to work.
>>
>> This fixes a regression present in 2.6.0 caused by the following commit:
>> fe1a9cbc339bb54d20f1ca4c1e8788d16944d5cf
>> block: Move some bdrv_*_all() functions to BB
>>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> ---
>> block/block-backend.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Worth testsuite coverage to prevent future regressions?
>
I'll look into it.
(Ugh, migration tests. wah. etc.)
--js
> At any rate,
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
>>
>> diff --git a/block/block-backend.c b/block/block-backend.c
>> index 34500e6..d1e875e 100644
>> --- a/block/block-backend.c
>> +++ b/block/block-backend.c
>> @@ -1122,7 +1122,7 @@ int blk_co_flush(BlockBackend *blk)
>>
>> int blk_flush(BlockBackend *blk)
>> {
>> - if (!blk_is_available(blk)) {
>> + if (!blk_is_inserted(blk)) {
>> return -ENOMEDIUM;
>> }
>>
>>
>
next prev parent reply other threads:[~2016-06-13 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 21:59 [Qemu-devel] [PATCH] block-backend: allow flush on devices with open tray John Snow
2016-06-10 22:42 ` Eric Blake
2016-06-13 17:57 ` John Snow [this message]
2016-06-12 2:26 ` Fam Zheng
2016-06-14 13:19 ` Max Reitz
2016-06-14 15:54 ` John Snow
2016-06-14 16:13 ` Max Reitz
2016-06-15 7:51 ` Kevin Wolf
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=1f901da0-d30d-76ef-f417-ee61d74bc421@redhat.com \
--to=jsnow@redhat.com \
--cc=eblake@redhat.com \
--cc=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).