From: Kevin Wolf <kwolf@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: idryomov@redhat.com, berrange@redhat.com, qemu-block@nongnu.org,
ct@flyingcircus.io, qemu-devel@nongnu.org, pbonzini@redhat.com,
idryomov@gmail.com, mreitz@redhat.com, dillaman@redhat.com
Subject: Re: [PATCH V2 for-6.2 0/2] fixes for bdrv_co_block_status
Date: Tue, 1 Feb 2022 15:39:28 +0100 [thread overview]
Message-ID: <YflB4LKDdf8ay1PU@redhat.com> (raw)
In-Reply-To: <20220113144426.4036493-1-pl@kamp.de>
Am 13.01.2022 um 15:44 hat Peter Lieven geschrieben:
> V1->V2:
> Patch 1: Treat a hole just like an unallocated area. [Ilya]
> Patch 2: Apply workaround only for pre-Quincy librbd versions and
> ensure default striping and non child images. [Ilya]
>
> Peter Lieven (2):
> block/rbd: fix handling of holes in .bdrv_co_block_status
> block/rbd: workaround for ceph issue #53784
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2022-02-01 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 14:44 [PATCH V2 for-6.2 0/2] fixes for bdrv_co_block_status Peter Lieven
2022-01-13 14:44 ` [PATCH V2 for-6.2 1/2] block/rbd: fix handling of holes in .bdrv_co_block_status Peter Lieven
2022-01-13 14:44 ` [PATCH V2 for-6.2 2/2] block/rbd: workaround for ceph issue #53784 Peter Lieven
2022-01-14 10:57 ` Ilya Dryomov
2022-01-17 14:23 ` Stefano Garzarella
2022-01-14 10:58 ` [PATCH V2 for-6.2 0/2] fixes for bdrv_co_block_status Ilya Dryomov
2022-01-19 14:57 ` Stefano Garzarella
2022-01-20 9:19 ` Peter Lieven
2022-01-25 10:09 ` Stefano Garzarella
2022-02-01 14:39 ` Kevin Wolf [this message]
2022-02-03 11:42 ` Peter Lieven
2022-02-03 12:14 ` Stefano Garzarella
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=YflB4LKDdf8ay1PU@redhat.com \
--to=kwolf@redhat.com \
--cc=berrange@redhat.com \
--cc=ct@flyingcircus.io \
--cc=dillaman@redhat.com \
--cc=idryomov@gmail.com \
--cc=idryomov@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--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).