On Tue, Aug 14, 2018 at 01:19:37PM +0200, Michal Privoznik wrote:
> So far the virLockSpaceAcquireResource() locks the first byte in
> the underlying file. But caller might want to lock other range.
> 
> Signed-off-by: Michal Privoznik <mpriv...@redhat.com>
> ---
>  src/locking/lock_daemon_dispatch.c |  3 +++
>  src/util/virlockspace.c            | 15 ++++++++++-----
>  src/util/virlockspace.h            |  4 ++++
>  tests/virlockspacetest.c           | 29 ++++++++++++++++++++++++-----
>  4 files changed, 41 insertions(+), 10 deletions(-)

Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

Reply via email to