diff options
| author | Michal Privoznik <mprivozn@redhat.com> | 2018-09-05 16:30:15 +0200 |
|---|---|---|
| committer | Michal Privoznik <mprivozn@redhat.com> | 2018-09-18 17:12:53 +0200 |
| commit | 3e26b476b5f322353bf0dcd8e3f037ca672b8c62 (patch) | |
| tree | cbd91fbf06843c251a8fcd9c50aa1441710a4374 /tests/securityselinuxtest.c | |
| parent | 8b8aefb3d6ae2139ea3d4ef6d7dd2c06f57f6075 (diff) | |
| download | libvirt-3e26b476b5f322353bf0dcd8e3f037ca672b8c62.tar.gz | |
security_manager: Load lock plugin on init
Now that we know what metadata lock manager user wishes to use we
can load it when initializing security driver. This is achieved
by adding new argument to virSecurityManagerNewDriver() and
subsequently to all functions that end up calling it.
The cfg.mk change is needed in order to allow lock_manager.h
inclusion in security driver without 'syntax-check' complaining.
This is safe thing to do as locking APIs will always exist (it's
only backend implementation that changes). However, instead of
allowing the include for all other drivers (like cpu, network,
and so on) allow it only for security driver. This will still
trigger the error if including from other drivers.
Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: John Ferlan <jferlan@redhat.com>
Diffstat (limited to 'tests/securityselinuxtest.c')
| -rw-r--r-- | tests/securityselinuxtest.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/securityselinuxtest.c b/tests/securityselinuxtest.c index a785e9a7da..5a19cb15fb 100644 --- a/tests/securityselinuxtest.c +++ b/tests/securityselinuxtest.c @@ -275,7 +275,7 @@ mymain(void) int ret = 0; virSecurityManagerPtr mgr; - if (!(mgr = virSecurityManagerNew("selinux", "QEMU", + if (!(mgr = virSecurityManagerNew("selinux", "QEMU", NULL, VIR_SECURITY_MANAGER_DEFAULT_CONFINED | VIR_SECURITY_MANAGER_PRIVILEGED))) { fprintf(stderr, "Unable to initialize security driver: %s\n", |