Re: [PATCH 8/9] wip: start virtiofsd

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

 



On Fri, Nov 1, 2019 at 1:18 PM Ján Tomko <jtomko@xxxxxxxxxx> wrote:
> +    if (qemuSecuritySetDaemonSocketLabel(driver->securityManager, vm->def) < 0)
> +        goto cleanup;
> +    fd = qemuOpenChrChardevUNIXSocket(chrdev);
> +    if (fd < 0)
> +        goto cleanup;
> +    if (qemuSecurityClearSocketLabel(driver->securityManager, vm->def) < 0)
> +        goto cleanup;

qemuSecurityClearSocketLabel() is not called in the
qemuOpenChrChardevUNIXSocket() error code path.  Is this correct?

> +static void
> +qemuExtVirtioFSdStop(virQEMUDriverPtr driver,
> +                     virDomainObjPtr vm,
> +                     virDomainFSDefPtr fs)
> +{

The daemon stops automatically when the vhost-user socket is closed by
QEMU.  Is it necessary to implement an explicit stop function?

Stefan

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




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux