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

[libvirt] [PATCH v1 0/6] Introduce metadata locking



All patches are for:

  https://bugzilla.redhat.com/show_bug.cgi?id=1524792

You can find them on my Github too:

  https://github.com/zippy2/libvirt/tree/disk_metadata_lock_alt


The locking by itself make very little sense. I have a patches waiting
that implement restoring original seclabels using XATTRs, that should go
on the top of these and can be also found on my Github:

  https://github.com/zippy2/libvirt/tree/seclabels

But those are for different bug therefore I'll send them separately.


And a bit of warning, I haven't bothered implementing this feature into
sanlock driver. The main reason for that was that we tell users to
prefer virtlockd over sanlock and if we really want them to switch lets
do it by the former offering more features than the latter.

Michal Prívozník (6):
  virlockspace: Introduce VIR_LOCK_SPACE_ACQUIRE_METADATA flag
  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 |   5 +-
 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            |  40 ++++-
 src/util/virlockspace.h            |   1 +
 11 files changed, 504 insertions(+), 48 deletions(-)

-- 
2.16.4


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