Re: [RFC PATCH 0/3] restructure memfd code

From: Mike Kravetz
Date: Mon Nov 20 2017 - 17:56:12 EST

On 11/20/2017 02:28 AM, Marc-Andrà Lureau wrote:
> Hi
> On Thu, Nov 9, 2017 at 2:41 AM, Mike Kravetz <mike.kravetz@xxxxxxxxxx> wrote:
>> With the addition of memfd hugetlbfs support, we now have the situation
>> where memfd depends on TMPFS -or- HUGETLBFS. Previously, memfd was only
>> supported on tmpfs, so it made sense that the code resides in shmem.c.
>> This patch series moves the memfd code to separate files (memfd.c and
>> memfd.h). It creates a new config option MEMFD_CREATE that is defined
>> if either TMPFS or HUGETLBFS is defined.
> That looks good to me
>> In the current code, memfd is only functional if TMPFS is defined. If
>> HUGETLFS is defined and TMPFS is not defined, then memfd functionality
>> will not be available for hugetlbfs. This does not cause BUGs, just a
>> potential lack of desired functionality.
> Indeed
>> Another way to approach this issue would be to simply make HUGETLBFS
>> depend on TMPFS.
>> This patch series is built on top of the Marc-Andrà Lureau v3 series
>> "memfd: add sealing to hugetlb-backed memory":
> Are you waiting for this series to be merged before resending as non-rfc?

Sort of.

I was hoping someone else would chime in on your series that adds file
sealing. Since they both are touching the same code, there will be
a bit of 'patch management' involved. One could argue that the config
dependency changes should go in before the file sealing code. Actually,
it should have gone in before the hugetlbfs memfd_create code. I'm not
sure if it matters too much right now.

I'm happy to do whatever people think is the right thing here.
Mike Kravetz