On Thu, Apr 11, 2019, 4:45 AM Chet Ramey <chet.ra...@case.edu> wrote:
> On 4/10/19 4:33 PM, konsolebox wrote: > > On Wed, Apr 10, 2019 at 11:15 PM Chet Ramey <chet.ra...@case.edu> wrote: > >> If we're going to go off into hypotheticals and speculation, it would be > >> nice if memfd_create were available universally. > > > > I see many parts in lib/* that adapts to available system features > > like mmap and MAP_ANONYMOUS. I don't see why memfd_create should be > > an exception. Using a volatile file is much better than forking, and > > this only requires a one-time implementation of a wrapper library > > function that returns -1 if the feature is not available in the > > system. It should be easy to integrate with the current code since it > > returns an fd. > > It has slightly inconvenient semantics, in that you can't open it more > than once, and if you can't do that, you can't convert it from read-write > to readonly. Perhaps it can be reopened via /dev/fd. -- konsolebox
