Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt

前往新版Gitcode，体验更适合开发者的 AI 搜索 >>

切换分支/标签
  1. 27 6月, 2020 2 次提交
  3. 26 6月, 2020 1 次提交
  5. 23 6月, 2020 1 次提交
  7. 19 6月, 2020 2 次提交
  9. 18 6月, 2020 3 次提交
  11. 16 6月, 2020 1 次提交
  13. 15 6月, 2020 1 次提交
  15. 25 5月, 2020 1 次提交
  17. 20 5月, 2020 3 次提交
  19. 27 4月, 2020 3 次提交
  21. 23 4月, 2020 2 次提交
  23. 21 4月, 2020 1 次提交
  25. 17 4月, 2020 1 次提交
    • M
      security: Introduce virSecurityManagerDomainSetPathLabelRO · 55cbb94e
      由 Michal Privoznik 提交于 
      This API allows drivers to separate out handling of @stdin_path
of virSecurityManagerSetAllLabel(). The thing is, the QEMU driver
uses transactions for virSecurityManagerSetAllLabel() which
relabels devices from inside of domain's namespace. This is what
we usually want. Except when resuming domain from a file. The
file is opened before any namespace is set up and the FD is
passed to QEMU to read the migration stream from. Because of
this, the file lives outside of the namespace and if it so
happens that the file is a block device (i.e. it lives under
/dev) its copy will be created in the namespace. But the FD that
is passed to QEMU points to the original living in the host and
not in the namespace. So relabeling the file inside the namespace
helps nothing.

But if we have a separate API for relabeling the restore file
then the QEMU driver can continue calling
virSecurityManagerSetAllLabel() with transactions enabled and
call this new API without transactions.

We already have an API for relabeling a single file
(virSecurityManagerDomainSetPathLabel()) but in case of SELinux
it uses @imagelabel (which allows RW access) and we want to use
@content_context (which allows RO access).
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
Reviewed-by: NErik Skultety <eskultet@redhat.com>
      55cbb94e
  27. 07 4月, 2020 2 次提交
  29. 27 3月, 2020 1 次提交
  31. 25 3月, 2020 1 次提交
  33. 23 3月, 2020 1 次提交
  35. 16 3月, 2020 1 次提交
  37. 14 3月, 2020 1 次提交
  39. 11 3月, 2020 1 次提交
  41. 05 3月, 2020 2 次提交
    • P
      VIR_FREE: Replace internals by g_clear_pointer · 09352cca
      由 Peter Krempa 提交于 
      Our implementation masks GCC warnings of uninitialized use of the passed
argument. After changing this I got a load of following warnings:

src/conf/virnetworkportdef.c: In function 'virNetworkPortDefSaveStatus':
/usr/include/glib-2.0/glib/gmem.h:136:8: error: 'path' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  136 |     if (_p)                \
      |        ^
src/conf/virnetworkportdef.c:447:11: note: 'path' was declared here
  447 |     char *path;
      |           ^~~~

For the curious, g_clear_pointer is still safe for arguments with
side-effect. Here's the pre-processed output of trying to do a
VIR_FREE(*(test2++)):

 do {
     typedef char _GStaticAssertCompileTimeAssertion_1[(sizeof *(&(*(test2++))) == sizeof (gpointer)) ? 1 : -1] __attribute__((__unused__));
     __typeof__((&(*(test2++)))) _pp = (&(*(test2++)));
     __typeof__(*(&(*(test2++)))) _ptr = *_pp;

     *_pp = ((void *)0);
     if (_ptr)
        (g_free) (_ptr);
 } while (0) ;
Signed-off-by: NPeter Krempa <pkrempa@redhat.com>
Reviewed-by: NJán Tomko <jtomko@redhat.com>
      09352cca
    • D
      src: set the OS level thread name · c85256b3
      由 Daniel P. Berrangé 提交于 
      Setting the thread name makes it easier to debug libvirtd
when many threads are running.
Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      c85256b3
  43. 04 3月, 2020 1 次提交
  45. 26 2月, 2020 2 次提交
  47. 25 2月, 2020 1 次提交
  49. 24 2月, 2020 3 次提交
  51. 23 2月, 2020 1 次提交