On 03/13/2017 09:39 PM, Fam Zheng wrote: > This flag clears out the "consistent read" permission that blk_new_open > requests. > > Signed-off-by: Fam Zheng <f...@redhat.com> > --- > block/block-backend.c | 2 +- > include/block/block.h | 1 + > 2 files changed, 2 insertions(+), 1 deletion(-) > > diff --git a/block/block-backend.c b/block/block-backend.c > index 5742c09..99428ee 100644 > --- a/block/block-backend.c > +++ b/block/block-backend.c > @@ -197,7 +197,7 @@ BlockBackend *blk_new_open(const char *filename, const > char *reference, > * caller of blk_new_open() doesn't make use of the permissions, but they > * shouldn't hurt either. We can still share everything here because the > * guest devices will add their own blockers if they can't share. */ > - perm = BLK_PERM_CONSISTENT_READ; > + perm = flags & BDRV_O_UNSAFE_READ ? 0 : BLK_PERM_CONSISTENT_READ;
A bit awkward that we have to add an option that requests negation of a permission under the hood, but looks like it is the least-invasive way to get what we want. Reviewed-by: Eric Blake <ebl...@redhat.com> -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
