Re: [libvirt] [PATCH] qemu: read backing chain names from qemu

> > But if it would satisfy your paranoia, I can certainly add a > verification step that the string being returned by qemu resolves to the > same inode being tracked by libvirt, at least in the case where the > <disk> element resolves to a filename rather than a network disk. I think it would be desirable, because while your current usage may be safe with these assumptions, if someone refactors this 6 months later they may not realize the security implications of this code.