[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[libvirt] [PATCH v2 0/7] Introduce metadata locking



v2 of:

https://www.redhat.com/archives/libvir-list/2018-August/msg00482.html

diff to v1:
- 1/6 from original patch set is replaced with different approach.
  As Dan suggested, virLockSpace accepts range to lock through its API
  and has new flag that tells it to wait for the lock to be acquired.


Michal Prívozník (7):
  virlockspace: Allow caller to specify start and length offset in
    virLockSpaceAcquireResource
  virlockspace: Introduce VIR_LOCK_SPACE_ACQUIRE_WAIT
  lock_driver.h: Introduce metadata flag
  lockd_driver_lockd: Implement metadata flag
  lock_driver_sanlock: Handle metadata flag gracefully
  domain_lock: Implement metadata locking
  qemu_security: Lock metadata while relabelling

 src/libvirt_private.syms           |   8 +
 src/locking/domain_lock.c          | 304 ++++++++++++++++++++++++++++++++++---
 src/locking/domain_lock.h          |  28 ++++
 src/locking/lock_daemon_dispatch.c |  13 +-
 src/locking/lock_driver.h          |   2 +
 src/locking/lock_driver_lockd.c    |  31 ++--
 src/locking/lock_driver_lockd.h    |   1 +
 src/locking/lock_driver_sanlock.c  |  25 ++-
 src/qemu/qemu_security.c           | 107 +++++++++++++
 src/util/virlockspace.c            |  25 ++-
 src/util/virlockspace.h            |   5 +
 tests/virlockspacetest.c           |  29 +++-
 12 files changed, 525 insertions(+), 53 deletions(-)

-- 
2.16.4


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]