When users will specify backing chain, we need to take into account what
was passed in them and/or inherit the data from the parents as we are
copying the data (labels, etc...) from the parent disk source.

Peter Krempa (12):
  storage: Extract common code to retrieve driver backend for support
    check
  storage: Add feature check for storage file backend supporting access
    check
  storage: Extract error reporting for broken chains
  security: selinux: Pass parent storage source into image labeling
    helper
  security: dac: Take parent security label into account
  security: selinux: Take parent security label into account
  qemu: domain: Simplify using DAC permissions of top of backing chain
  qemu: domain: Extract setup for disk source secrets
  qemu: domain: Destroy secrets for complete backing chain
  qemu: domain: Remove pointless alias check
  qemu: domain: Prepare TLS data for the whole backing chain
  qemu: domain: skip chain detection to end of backing chain

 src/qemu/qemu_domain.c          | 177 ++++++++++++++++++++++++++--------------
 src/qemu/qemu_domain.h          |   6 +-
 src/qemu/qemu_driver.c          |   6 +-
 src/qemu/qemu_hotplug.c         |   2 +-
 src/qemu/qemu_process.c         |   2 +-
 src/security/security_dac.c     |  38 +++++++--
 src/security/security_selinux.c |  26 +++---
 src/storage/storage_source.c    | 110 ++++++++++++++++---------
 src/storage/storage_source.h    |   5 ++
 9 files changed, 246 insertions(+), 126 deletions(-)

-- 
2.14.1

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