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

[Khalid Aziz]

On Wed, 2017-11-08 at 17:41 -0800, Mike Kravetz 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.
> 
> 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.
> 
> 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":
> http://lkml.kernel.org/r/20171107122800.25517-1-marcandre.lureau@redh
> at.com
> 
> Mike Kravetz (3):
> Â mm: hugetlbfs: move HUGETLBFS_I outside #ifdef CONFIG_HUGETLBFS
> Â mm: memfd: split out memfd for use by multiple filesystems
> Â mm: memfd: remove memfd code from shmem files and use new memfd
> files
> 

Hi Mike,

This looks like a useful change. After applying patch 2, you end up
with duplicate definitions of number of symbols though. Although those
duplicates will not cause compilation problems since memfd.c is not
compiled until after patch 3 has been applied, would it make more sense
to combine moving of all code in one patch?

--
Khalid