Re: [PATCH v7 0/5] fix & merge block_status_above and is_allocated_above

2020-10-09 Thread Stefan Hajnoczi
On Thu, Sep 24, 2020 at 10:39:58PM +0300, Vladimir Sementsov-Ogievskiy wrote: > Hi all! > > These series are here to address the following problem: > block-status-above functions may consider space after EOF of > intermediate backing files as unallocated, which is wrong, as these > backing files

Re: [PATCH v7 0/5] fix & merge block_status_above and is_allocated_above

2020-09-25 Thread Vladimir Sementsov-Ogievskiy
It's all because underlying "[PATCH v9 0/7] coroutines: generate wrapper code" series, I've answered in "[PATCH v9 0/7] coroutines: generate wrapper code" thread. 25.09.2020 00:45, no-re...@patchew.org wrote: Patchew URL:

Re: [PATCH v7 0/5] fix & merge block_status_above and is_allocated_above

2020-09-24 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20200924194003.22080-1-vsement...@virtuozzo.com/ Hi, This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT

[PATCH v7 0/5] fix & merge block_status_above and is_allocated_above

2020-09-24 Thread Vladimir Sementsov-Ogievskiy
Hi all! These series are here to address the following problem: block-status-above functions may consider space after EOF of intermediate backing files as unallocated, which is wrong, as these backing files are the reason of producing zeroes, we never go further by backing chain after a short