[libvirt] [PATCH] util: fix mount issue by moving NULL value to "none" in syscall.

After running libvirt daemon with valgrind tools, some errors are appearing when you try to start a domain. One example: ==18012== Syscall param mount(type) points to unaddressable byte(s) ==18012==at 0x6FEE3CA: mount (syscall-template.S:78) ==18012==by 0x531344D: virFileMoveMount (virfile

Re: [libvirt] [PATCH] util: fix mount issue by moving NULL value to "none" in syscall.

On 06/26/2018 05:18 AM, Julio Faracco wrote: > After running libvirt daemon with valgrind tools, some errors are > appearing when you try to start a domain. One example: > > ==18012== Syscall param mount(type) points to unaddressable byte(s) > ==18012==at 0x6FEE3CA: mount (syscall-template.S:7