I've had these patches sitting around for a few months. They are not critical, but might be desirable in some unusual configurations. They depend on code in mmotm and linux-next that is not yet upstream, and apply to those repos. 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. When this was sent as a RFC, one comment suggested combining patches 2 and 3 so that we would not have 'new unused' files between patches. If this is desired, I can make the change. For me, it is easier to read as separate patches. 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 fs/Kconfig | 3 + fs/fcntl.c | 2 +- include/linux/hugetlb.h | 27 ++-- include/linux/memfd.h | 16 +++ include/linux/shmem_fs.h | 13 -- mm/Makefile | 1 + mm/memfd.c | 341 +++++++++++++++++++++++++++++++++++++++++++++++ mm/shmem.c | 323 -------------------------------------------- 8 files changed, 378 insertions(+), 348 deletions(-) create mode 100644 include/linux/memfd.h create mode 100644 mm/memfd.c -- 2.13.6 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
