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

Michal Privoznik posted 7 patches 5 years, 7 months ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/libvirt tags/patchew/cover.1534245398.git.mprivozn@redhat.com
Test syntax-check passed
There is a newer version of this series
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(-)
[libvirt] [PATCH v2 0/7] Introduce metadata locking
Posted by Michal Privoznik 5 years, 7 months ago
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

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH v2 0/7] Introduce metadata locking
Posted by no-reply@patchew.org 5 years, 7 months ago
Hi,

This series was run against 'syntax-check' test by patchew.org, which failed, please find the details below:

Type: series
Message-id: cover.1534245398.git.mprivozn@redhat.com
Subject: [libvirt] [PATCH v2 0/7] Introduce metadata locking

=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a commit that has the patches applied on top of "base"
# branch
time bash -c './autogen.sh && make syntax-check'
=== TEST SCRIPT END ===

Updating bcb55ab053bc79561b55d0394490f4b64e0f2d01
>From https://github.com/patchew-project/libvirt
   ff7bd6a245..b0451117b3  master     -> master
 * [new tag]               patchew/20180814114440.20803-1-abologna@redhat.com -> patchew/20180814114440.20803-1-abologna@redhat.com
Switched to a new branch 'test'
de813e44ab qemu_security: Lock metadata while relabelling
718359e105 domain_lock: Implement metadata locking
77e0f31573 lock_driver_sanlock: Handle metadata flag gracefully
a40a747b66 lockd_driver_lockd: Implement metadata flag
8759856c94 lock_driver.h: Introduce metadata flag
3314c0a08f virlockspace: Introduce VIR_LOCK_SPACE_ACQUIRE_WAIT
400bd7189d virlockspace: Allow caller to specify start and length offset in virLockSpaceAcquireResource

=== OUTPUT BEGIN ===
Updating submodules...
Submodule 'gnulib' (https://git.savannah.gnu.org/git/gnulib.git/) registered for path '.gnulib'
Submodule 'keycodemapdb' (https://gitlab.com/keycodemap/keycodemapdb.git) registered for path 'src/keycodemapdb'
Cloning into '/var/tmp/patchew-tester-tmp-i2jn955t/src/.gnulib'...
fatal: unable to access 'https://git.savannah.gnu.org/git/gnulib.git/': The requested URL returned error: 502
fatal: clone of 'https://git.savannah.gnu.org/git/gnulib.git/' into submodule path '/var/tmp/patchew-tester-tmp-i2jn955t/src/.gnulib' failed
Failed to clone '.gnulib'. Retry scheduled
Cloning into '/var/tmp/patchew-tester-tmp-i2jn955t/src/src/keycodemapdb'...
Cloning into '/var/tmp/patchew-tester-tmp-i2jn955t/src/.gnulib'...
fatal: unable to access 'https://git.savannah.gnu.org/git/gnulib.git/': The requested URL returned error: 502
fatal: clone of 'https://git.savannah.gnu.org/git/gnulib.git/' into submodule path '/var/tmp/patchew-tester-tmp-i2jn955t/src/.gnulib' failed
Failed to clone '.gnulib' a second time, aborting
error: Updating submodules failed

real	0m6.736s
user	0m0.751s
sys	0m0.443s
=== OUTPUT END ===

Test command exited with code: 1

---
Email generated automatically by Patchew [http://patchew.org/].
Please send your feedback to patchew-devel@redhat.com

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