On 21.02.2017 15:58, Kevin Wolf wrote: > The backup block job doesn't have very complicated requirements: It > needs to read from the source and write to the target, but it's fine > with either side being changed. The only restriction is that we can't > resize the image because the job uses a cached value. > > qemu-iotests 055 needs to be changed because it used a target which was > already attached to a virtio-blk device. The permission system correctly > forbids this (virtio-blk can't accept another writer with its default > share-rw=off). > > Signed-off-by: Kevin Wolf <kw...@redhat.com> > --- > block/backup.c | 15 ++++++++++----- > tests/qemu-iotests/055 | 11 +++++++---- > 2 files changed, 17 insertions(+), 9 deletions(-)
Not sure how much sense it makes to allow other writers on the target node, but it's not as if the backup block job itself would care: Reviewed-by: Max Reitz <mre...@redhat.com>
signature.asc
Description: OpenPGP digital signature
