Comment 27 for bug 1626972
Revision history for this message
| Rafael David Tinoco (rafaeldtinoco) wrote Re: [Qemu-devel] [Bug 1626972] Re: [PATCH] util: secure memfd_create fallback mechanism | #27 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
> On Oct 04, 2016, at 10:50, Marc-André Lureau <email address hidden> wrote:
>
> What about having a single config parameter as a place to put all vhost logs for all drives for a single instance ? Remove the memfd implementation with all the memfd shared_memory option ? Replace it with a open+unlink+
>
>
> I fail to see your point, memfd is superior to open+unlink and has other advantages with sealing etc.
I was just summarising needs based on previous statement from Daniel:
> This makes me wonder about the memfd_create() code path too - we'll
> again not want that external process to be granted access to arbitrary
> FDs of QEMU's and I'm not sure of a way to get the memfd FD to have
> a specific label. So I think it is possible that when using libvirt
> we'll want the ability to tell QEMU to *always* use an explicit file
> in a path libvirt specifies, and never use memfd even if available.
>
> Regards,
> Daniel