On 12/15/2017 02:04 AM, Fam Zheng wrote:
> Shared write lock is not strictly necessary for creating the overlay image, if
> all what we want is to probe the size.
Theoretically, the size could be changing due to a resize operation.
But realistically, even if that happens, we will (hopefully) see e
Shared write lock is not strictly necessary for creating the overlay image, if
all what we want is to probe the size.
Fam Zheng (2):
block: Open backing image in force share mode for size probe
iotests: Test creating overlay when guest running
block.c| 3 ++-
tests/qemu-i
