Changes in Kconfig

cd35b6cb - nfs: add missing selections of CONFIG_CRC32

Tue, 01 Apr 2025 22:02:21 +0000

nfs: add missing selections of CONFIG_CRC32nfs.ko, nfsd.ko, and lockd.ko all use crc32_le(), which is availableonly when CONFIG_CRC32 is enabled. But the only NFS kconfig option thatselected CONFIG_CRC32 was CONFIG_NFS_DEBUG, which is client-specific anddid not actually guard the use of crc32_le() even on the client.The code worked around this bug by only actually calling crc32_le() whenCONFIG_CRC32 is built-in, instead hard-coding '0' in other cases. Thisavoided randconfig build errors, and in real kernels the fallback codewas unlikely to be reached since CONFIG_CRC32 is 'default y'. But, thisreally needs to just be done properly, especially now that I'm planningto update CONFIG_CRC32 to not be 'default y'.Therefore, make CONFIG_NFS_FS, CONFIG_NFSD, and CONFIG_LOCKD selectCONFIG_CRC32. Then remove the fallback code that becomes unnecessary,as well as the selection of CONFIG_CRC32 from CONFIG_NFS_DEBUG.Fixes: 1264a2f053a3 ("NFS: refactor code for calculating the crc32 hash of a filehandle")Signed-off-by: Eric Biggers Acked-by: Anna Schumaker Signed-off-by: Chuck Lever List of files: /linux-6.15/fs/Kconfig

d65917c4 - mm/sparse: allow for alternate vmemmap section init at boot

Fri, 28 Feb 2025 18:29:11 +0000

mm/sparse: allow for alternate vmemmap section init at bootAdd functions that are called just before the per-section memmap isinitialized and just before the memmap page structures are initialized. They are called sparse_vmemmap_init_nid_early andsparse_vmemmap_init_nid_late, respectively.This allows for mm subsystems to add calls to initialize memmap and pagestructures in a specific way, if using SPARSEMEM_VMEMMAP. Specifically,hugetlb can pre-HVO bootmem allocated pages that way, so that no time andresources are wasted on allocating vmemmap pages, only to free them later(and possibly unnecessarily running the system out of memory in theprocess).Refactor some code and export a few convenience functions for externaluse.In sparse_init_nid, skip any sections that are already initialized, e.g. they have been initialized by sparse_vmemmap_init_nid_early already.The hugetlb code to use these functions will be added in a later commit.Export section_map_size, as any alternate memmap init code will want touse it.The internal config option to enable this is SPARSEMEM_VMEMMAP_PREINIT,which is selected if an architecture-specific option,ARCH_WANT_HUGETLB_VMEMMAP_PREINIT, is set. In the future, if othersubsystems want to do preinit too, they can do it in a similar fashion.The internal config option is there because a section flag is used, andthe number of flags available is architecture-dependent (see mmzone.h). Architecures can decide if there is room for the flag when enablingoptions that select SPARSEMEM_VMEMMAP_PREINIT.Fortunately, as of right now, all sparse vmemmap using architectures dohave room.Link: https://lkml.kernel.org/r/20250228182928.2645936-11-fvdl@google.comSigned-off-by: Frank van der Linden Cc: Johannes Weiner Cc: Alexander Gordeev Cc: Andy Lutomirski Cc: Arnd Bergmann Cc: Dan Carpenter Cc: Dave Hansen Cc: David Hildenbrand Cc: Heiko Carstens Cc: Joao Martins Cc: Madhavan Srinivasan Cc: Michael Ellerman Cc: Muchun Song Cc: Oscar Salvador Cc: Peter Zijlstra Cc: Roman Gushchin (Cruise) Cc: Usama Arif Cc: Vasily Gorbik Cc: Yu Zhao Cc: Zi Yan Signed-off-by: Andrew Morton List of files: /linux-6.15/fs/Kconfig

448fa701 - sysv: Remove the filesystem

Thu, 20 Feb 2025 16:39:41 +0000

sysv: Remove the filesystemSince 2002 (change "Replace BKL for chain locking with sysvfs-privaterwlock") the sysv filesystem was doing IO under a rwlock in itsget_block() function (yes, a non-sleepable lock hold over a functionused to read inode metadata for all reads and writes). Nobody noticeduntil syzbot in 2023 [1]. This shows nobody is using the filesystem.Just drop it.[1] https://lore.kernel.org/all/0000000000000ccf9a05ee84f5b0@google.com/Signed-off-by: Jan Kara Link: https://lore.kernel.org/r/20250220163940.10155-2-jack@suse.czReviewed-by: Jeff Layton Reviewed-by: "Darrick J. Wong" Signed-off-by: Christian Brauner List of files: /linux-6.15/fs/Kconfig

fb6f20ec - reiserfs: The last commit

Thu, 17 Oct 2024 10:28:23 +0000

reiserfs: The last commitDeprecation period of reiserfs ends with the end of this year so it istime to remove it from the kernel.Acked-by: Darrick J. Wong Acked-by: Christian Brauner Signed-off-by: Jan Kara List of files: /linux-6.15/fs/Kconfig

009b15b5 - nfs_common: fix Kconfig for NFS_COMMON_LOCALIO_SUPPORT

Thu, 03 Oct 2024 19:34:59 +0000

nfs_common: fix Kconfig for NFS_COMMON_LOCALIO_SUPPORTThe 'default n' that was in NFS_COMMON_LOCALIO_SUPPORT caused theseextra defaults to be missed: default y if NFSD=y || NFS_FS=y default m if NFSD=m && NFS_FS=mRemove the 'default n' for NFS_COMMON_LOCALIO_SUPPORT so that thecorrect tristate is selected based on how NFSD and NFS_FS areconfigured. This fixes the reported case where NFS_FS=y butNFS_COMMON_LOCALIO_SUPPORT=m, it is now correctly set to =y.In addition, add extra 'depends on NFS_LOCALIO' toNFS_COMMON_LOCALIO_SUPPORT so that if NFS_LOCALIO isn't set thenNFS_COMMON_LOCALIO_SUPPORT will not be either.Reported-by: kernel test robot Closes: https://lore.kernel.org/oe-kbuild-all/202410031944.hMCFY9BO-lkp@intel.com/Signed-off-by: Mike Snitzer Signed-off-by: Anna Schumaker List of files: /linux-6.15/fs/Kconfig

2a33a85b - nfs_common: add NFS LOCALIO auxiliary protocol enablement

Thu, 05 Sep 2024 19:09:48 +0000

nfs_common: add NFS LOCALIO auxiliary protocol enablementfs/nfs_common/nfslocalio.c provides interfaces that enable an NFSclient to generate a nonce (single-use UUID) and associated nfs_uuid_tstruct, register it with nfs_common for subsequent lookup andverification by the NFS server and if matched the NFS server populatesmembers in the nfs_uuid_t struct.nfs_common's nfs_uuids list is the basis for localio enablement, assuch it has members that point to nfsd memory for direct use by theclient (e.g. 'net' is the server's network namespace, through it theclient can access nn->nfsd_serv).This commit also provides the base nfs_uuid_t interfaces to allowproper net namespace refcounting for the LOCALIO use case.CONFIG_NFS_LOCALIO controls the nfs_common, NFS server and NFS clientenablement for LOCALIO. If both NFS_FS=m and NFSD=m thenNFS_COMMON_LOCALIO_SUPPORT=m and nfs_localio.ko is built (and providesnfs_common's LOCALIO support). # lsmod | grep nfs_localio nfs_localio 12288 2 nfsd,nfs sunrpc 745472 35 nfs_localio,nfsd,auth_rpcgss,lockd,nfsv3,nfsSigned-off-by: Mike Snitzer Co-developed-by: NeilBrown Signed-off-by: NeilBrown Reviewed-by: Jeff Layton Signed-off-by: Anna Schumaker List of files: /linux-6.15/fs/Kconfig

188cac58 - mm/hugetlb: enforce that PMD PT sharing has split PMD PT locks

Fri, 26 Jul 2024 15:07:27 +0000

mm/hugetlb: enforce that PMD PT sharing has split PMD PT locksSharing page tables between processes but falling back to per-MM pagetable locks cannot possibly work.So, let's make sure that we do have split PMD locks by adding a newKconfig option and letting that depend on CONFIG_SPLIT_PMD_PTLOCKS.Link: https://lkml.kernel.org/r/20240726150728.3159964-3-david@redhat.comSigned-off-by: David Hildenbrand Acked-by: Mike Rapoport (Microsoft) Cc: Alexander Viro Cc: Borislav Petkov Cc: Boris Ostrovsky Cc: Christian Brauner Cc: Christophe Leroy Cc: Dave Hansen Cc: "H. Peter Anvin" Cc: Ingo Molnar Cc: Juergen Gross Cc: Michael Ellerman Cc: Muchun Song Cc: "Naveen N. Rao" Cc: Nicholas Piggin Cc: Oscar Salvador Cc: Peter Xu Cc: Russell King Cc: Thomas Gleixner Signed-off-by: Andrew Morton List of files: /linux-6.15/fs/Kconfig

9d9539db - pidfs: remove config option

Tue, 12 Mar 2024 09:39:44 +0000

pidfs: remove config optionAs Linus suggested this enables pidfs unconditionally. A key property toretain is the ability to compare pidfds by inode number (cf. [1]).That's extremely helpful just as comparing namespace file descriptors byinode number is. They are used in a variety of scenarios where they needto be compared, e.g., when receiving a pidfd via SO_PEERPIDFD from asocket to trivially authenticate a the sender and various otheruse-cases.For 64bit systems this is pretty trivial to do. For 32bit it's slightlymore annoying as we discussed but we simply add a dumb ida basedallocator that gets used on 32bit. This gives the same guarantees aboutinode numbers on 64bit without any overflow risk. Practically, we'llnever run into overflow issues because we're constrained by the numberof processes that can exist on 32bit and by the number of open filesthat can exist on a 32bit system. On 64bit none of this matters andthings are very simple.If 32bit also needs the uniqueness guarantee they can simply parse thecontents of /proc//fd/. The uniqueness guarantees have avariety of use-cases. One of the most obvious ones is that they willmake pidfiles (or "pidfdfiles", I guess) reliable as the uniqueidentifier can be placed into there that won't be reycled. Also afrequent request.Note, I took the chance and simplified path_from_stashed() even further.Instead of passing the inode number explicitly to path_from_stashed() welet the filesystem handle that internally. So path_from_stashed() endsup even simpler than it is now. This is also a good solution allowingthe cleanup code to be clean and consistent between 32bit and 64bit. Thecleanup path in prepare_anon_dentry() is also switched around so we putthe inode before the dentry allocation. This means we only have to callthe cleanup handler for the filesystem's inode data once and can rely->evict_inode() otherwise.Aside from having to have a bit of extra code for 32bit it actually endsup a nice cleanup for path_from_stashed() imho.Tested on both 32 and 64bit including error injection.Link: https://github.com/systemd/systemd/pull/31713 [1]Link: https://lore.kernel.org/r/20240312-dingo-sehnlich-b3ecc35c6de7@braunerSigned-off-by: Christian Brauner Signed-off-by: Linus Torvalds List of files: /linux-6.15/fs/Kconfig

26d1dc6b - hugetlb: have CONFIG_HUGETLBFS select CONFIG_PADATA

Thu, 22 Feb 2024 14:04:19 +0000

hugetlb: have CONFIG_HUGETLBFS select CONFIG_PADATAAllow hugetlb use padata_do_multithreaded for parallel initialization. Select CONFIG_PADATA in this case.Link: https://lkml.kernel.org/r/20240222140422.393911-7-gang.li@linux.devSigned-off-by: Gang Li Tested-by: David Rientjes Reviewed-by: Muchun Song Tested-by: Paul E. McKenney Acked-by: Daniel Jordan Cc: Alexey Dobriyan Cc: David Hildenbrand Cc: Jane Chu Cc: Mike Kravetz Cc: Randy Dunlap Cc: Steffen Klassert Cc: Tim Chen Signed-off-by: Andrew Morton List of files: /linux-6.15/fs/Kconfig

cb12fd8e - pidfd: add pidfs

Mon, 12 Feb 2024 15:32:38 +0000

pidfd: add pidfsThis moves pidfds from the anonymous inode infrastructure to a tinypseudo filesystem. This has been on my todo for quite a while as it willunblock further work that we weren't able to do simply because of thevery justified limitations of anonymous inodes. Moving pidfds to a tinypseudo filesystem allows:* statx() on pidfds becomes useful for the first time.* pidfds can be compared simply via statx() and then comparing inode numbers.* pidfds have unique inode numbers for the system lifetime.* struct pid is now stashed in inode->i_private instead of file->private_data. This means it is now possible to introduce concepts that operate on a process once all file descriptors have been closed. A concrete example is kill-on-last-close.* file->private_data is freed up for per-file options for pidfds.* Each struct pid will refer to a different inode but the same struct pid will refer to the same inode if it's opened multiple times. In contrast to now where each struct pid refers to the same inode. Even if we were to move to anon_inode_create_getfile() which creates new inodes we'd still be associating the same struct pid with multiple different inodes.The tiny pseudo filesystem is not visible anywhere in userspace exactlylike e.g., pipefs and sockfs. There's no lookup, there's no complexinode operations, nothing. Dentries and inodes are always deleted whenthe last pidfd is closed.We allocate a new inode for each struct pid and we reuse that inode forall pidfds. We use iget_locked() to find that inode again based on theinode number which isn't recycled. We allocate a new dentry for eachpidfd that uses the same inode. That is similar to anonymous inodeswhich reuse the same inode for thousands of dentries. For pidfds we'retalking way less than that. There usually won't be a lot of concurrentopeners of the same struct pid. They can probably often be counted ontwo hands. I know that systemd does use separate pidfd for the samestruct pid for various complex process tracking issues. So I think withthat things actually become way simpler. Especially because we don'thave to care about lookup. Dentries and inodes continue to be alwaysdeleted.The code is entirely optional and fairly small. If it's not selected wefallback to anonymous inodes. Heavily inspired by nsfs which uses asimilar stashing mechanism just for namespaces.Link: https://lore.kernel.org/r/20240213-vfs-pidfd_fs-v1-2-f863f58cfce1@kernel.orgSigned-off-by: Christian Brauner List of files: /linux-6.15/fs/Kconfig

1df4ca01 - dax: check for data cache aliasing at runtime

Thu, 15 Feb 2024 14:46:31 +0000

dax: check for data cache aliasing at runtimeReplace the following fs/Kconfig:FS_DAX dependency: depends on !(ARM || MIPS || SPARC)By a runtime check within alloc_dax(). This runtime check returnsERR_PTR(-EOPNOTSUPP) if the @ops parameter is non-NULL (which meansthe kernel is using an aliased mapping) on an architecture whichhas data cache aliasing.Change the return value from NULL to PTR_ERR(-EOPNOTSUPP) forCONFIG_DAX=n for consistency.This is done in preparation for using cpu_dcache_is_aliasing() in afollowing change which will properly support architectures which detectdata cache aliasing at runtime.Link: https://lkml.kernel.org/r/20240215144633.96437-8-mathieu.desnoyers@efficios.comFixes: d92576f1167c ("dax: does not work correctly with virtual aliasing caches")Signed-off-by: Mathieu Desnoyers Reviewed-by: Dan Williams Cc: Dan Williams Cc: Vishal Verma Cc: Dave Jiang Cc: Matthew Wilcox Cc: Arnd Bergmann Cc: Russell King Cc: Alasdair Kergon Cc: Christoph Hellwig Cc: Dave Chinner Cc: Heiko Carstens Cc: kernel test robot Cc: Michael Sclafani Cc: Mike Snitzer Cc: Mikulas Patocka Signed-off-by: Andrew Morton List of files: /linux-6.15/fs/Kconfig

7ffa8f3d - fs: Remove NTFS classic

Mon, 15 Jan 2024 07:20:25 +0000

fs: Remove NTFS classicThe replacement, NTFS3, was merged over two years ago. It is now time toremove the original from the tree as it is the last user of several APIs,and it is not worth changing.Signed-off-by: Matthew Wilcox (Oracle) Link: https://lore.kernel.org/r/20240115072025.2071931-1-willy@infradead.orgAcked-by: Namjae Jeon Acked-by: Dave Chinner Cc: Anton Altaparmakov Cc: Namjae Jeon Signed-off-by: Christian Brauner List of files: /linux-6.15/fs/Kconfig

47757ea8 - netfs, fscache: Move fs/fscache/* into fs/netfs/

Mon, 20 Nov 2023 15:29:09 +0000

netfs, fscache: Move fs/fscache/* into fs/netfs/There's a problem with dependencies between netfslib and fscache as eachwants to access some functions of the other. Deal with this by movingfs/fscache/* into fs/netfs/ and renaming those files to begin with"fscache-".For the moment, the moved files are changed as little as possible and anfscache module is still built. A subsequent patch will integrate them.Signed-off-by: David Howells Reviewed-by: Jeff Layton cc: Christian Brauner cc: linux-fsdevel@vger.kernel.orgcc: linux-cachefs@redhat.com List of files: /linux-6.15/fs/Kconfig

f91a704f - fs: prepare for stackable filesystems backing file helpers

Mon, 02 Oct 2023 14:19:46 +0000

fs: prepare for stackable filesystems backing file helpersIn preparation for factoring out some backing file io helpers fromoverlayfs, move backing_file_open() into a new file fs/backing-file.cand header.Add a MAINTAINERS entry for stackable filesystems and add a KconfigFS_STACK which stackable filesystems need to select.For now, the backing_file struct, the backing_file alloc/free functionsand the backing_file_real_path() accessor remain internal to file_table.c.We may change that in the future.Signed-off-by: Amir Goldstein List of files: /linux-6.15/fs/Kconfig

cddba0af - fs/Kconfig: make hugetlbfs a menuconfig

Fri, 24 Nov 2023 15:19:02 +0000

fs/Kconfig: make hugetlbfs a menuconfigHugetlb vmemmap default option (HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON)is a sub-option to hugetlbfs, but it shows in the same level as hugetlbfsitself, under "Pesudo filesystems".Make the vmemmap option a sub-option to hugetlbfs, by changing hugetlbfsinto a menuconfig. When moving it, fix a typo 'v' spot by Randy.Link: https://lkml.kernel.org/r/20231124151902.1075697-1-peterx@redhat.comSigned-off-by: Peter Xu Reviewed-by: Muchun Song Cc: Mike Kravetz Cc: Randy Dunlap Signed-off-by: Andrew Morton List of files: /linux-6.15/fs/Kconfig

4a3ef6be - mm/hugetlb: have CONFIG_HUGETLB_PAGE select CONFIG_XARRAY_MULTI

Mon, 04 Dec 2023 18:32:34 +0000

mm/hugetlb: have CONFIG_HUGETLB_PAGE select CONFIG_XARRAY_MULTIAfter commit a08c7193e4f1 "mm/filemap: remove hugetlb special casing infilemap.c", hugetlb pages are stored in the page cache in base page sizedindexes. This leads to multi index stores in the xarray which is onlysupporting through CONFIG_XARRAY_MULTI. The other page cache user ofmulti index stores ,THP, selects XARRAY_MULTI. Have CONFIG_HUGETLB_PAGEfollow this behavior as well to avoid the BUG() with a CONFIG_HUGETLB_PAGE&& !CONFIG_XARRAY_MULTI config.Link: https://lkml.kernel.org/r/20231204183234.348697-1-sidhartha.kumar@oracle.comFixes: a08c7193e4f1 ("mm/filemap: remove hugetlb special casing in filemap.c")Signed-off-by: Sidhartha Kumar Reported-by: Al Viro Cc: Mike Kravetz Cc: Muchun Song Signed-off-by: Andrew Morton List of files: /linux-6.15/fs/Kconfig

1c6fdbd8 - bcachefs: Initial commit

Fri, 17 Mar 2017 06:18:50 +0000

bcachefs: Initial commitInitially forked from drivers/md/bcache, bcachefs is a new copy-on-writefilesystem with every feature you could possibly want.Website: https://bcachefs.orgSigned-off-by: Kent Overstreet List of files: /linux-6.15/fs/Kconfig

cf8e8658 - arch: Remove Itanium (IA-64) architecture

Thu, 20 Oct 2022 13:54:33 +0000

arch: Remove Itanium (IA-64) architectureThe Itanium architecture is obsolete, and an informal survey [0] revealsthat any residual use of Itanium hardware in production is mostly HP-UXor OpenVMS based. The use of Linux on Itanium appears to be limited toenthusiasts that occasionally boot a fresh Linux kernel to see whetherthings are still working as intended, and perhaps to churn out somedistro packages that are rarely used in practice.None of the original companies behind Itanium still produce or supportany hardware or software for the architecture, and it is listed as'Orphaned' in the MAINTAINERS file, as apparently, none of the engineersthat contributed on behalf of those companies (nor anyone else, for thatmatter) have been willing to support or maintain the architectureupstream or even be responsible for applying the odd fix. The Intelfirmware team removed all IA-64 support from the Tianocore/EDK2reference implementation of EFI in 2018. (Itanium is the originalarchitecture for which EFI was developed, and the way Linux supports itdeviates significantly from other architectures.) Some distros, such asDebian and Gentoo, still maintain [unofficial] ia64 ports, but many havedropped support years ago.While the argument is being made [1] that there is a 'for the commongood' angle to being able to build and run existing projects such as theGrid Community Toolkit [2] on Itanium for interoperability testing, thefact remains that none of those projects are known to be deployed onLinux/ia64, and very few people actually have access to such a system inthe first place. Even if there were ways imaginable in which Linux/ia64could be put to good use today, what matters is whether anyone isactually doing that, and this does not appear to be the case.There are no emulators widely available, and so boot testing Itanium isgenerally infeasible for ordinary contributors. GCC still supports IA-64but its compile farm [3] no longer has any IA-64 machines. GLIBC wouldlike to get rid of IA-64 [4] too because it would permit some overduecode cleanups. In summary, the benefits to the ecosystem of having IA-64be part of it are mostly theoretical, whereas the maintenance overheadof keeping it supported is real.So let's rip off the band aid, and remove the IA-64 arch code entirely.This follows the timeline proposed by the Debian/ia64 maintainer [5],which removes support in a controlled manner, leaving IA-64 in a knowngood state in the most recent LTS release. Other projects will followonce the kernel support is removed.[0] https://lore.kernel.org/all/CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com/[1] https://lore.kernel.org/all/0075883c-7c51-00f5-2c2d-5119c1820410@web.de/[2] https://gridcf.org/gct-docs/latest/index.html[3] https://cfarm.tetaneutral.net/machines/list/[4] https://lore.kernel.org/all/87bkiilpc4.fsf@mid.deneb.enyo.de/[5] https://lore.kernel.org/all/ff58a3e76e5102c94bb5946d99187b358def688a.camel@physik.fu-berlin.de/Acked-by: Tony Luck Signed-off-by: Ard Biesheuvel List of files: /linux-6.15/fs/Kconfig

0b6f1582 - mm/vmemmap optimization: split hugetlb and devdax vmemmap optimization

Mon, 24 Jul 2023 19:07:53 +0000

mm/vmemmap optimization: split hugetlb and devdax vmemmap optimizationArm disabled hugetlb vmemmap optimization [1] because hugetlb vmemmapoptimization includes an update of both the permissions (writeable toread-only) and the output address (pfn) of the vmemmap ptes. That is notsupported without unmapping of pte(marking it invalid) by somearchitectures.With DAX vmemmap optimization we don't require such pte updates andarchitectures can enable DAX vmemmap optimization while having hugetlbvmemmap optimization disabled. Hence split DAX optimization support intoa different config.s390, loongarch and riscv don't have devdax support. So the DAX config isnot enabled for them. With this change, arm64 should be able to selectDAX optimization[1] commit 060a2c92d1b6 ("arm64: mm: hugetlb: Disable HUGETLB_PAGE_OPTIMIZE_VMEMMAP")Link: https://lkml.kernel.org/r/20230724190759.483013-8-aneesh.kumar@linux.ibm.comSigned-off-by: Aneesh Kumar K.V Cc: Catalin Marinas Cc: Christophe Leroy Cc: Dan Williams Cc: Joao Martins Cc: Michael Ellerman Cc: Mike Kravetz Cc: Muchun Song Cc: Nicholas Piggin Cc: Oscar Salvador Cc: Will Deacon Signed-off-by: Andrew Morton List of files: /linux-6.15/fs/Kconfig

626e98cb - mm: make MEMFD_CREATE into a selectable config option

Fri, 30 Jun 2023 09:08:53 +0000

mm: make MEMFD_CREATE into a selectable config optionThe memfd_create() syscall, enabled by CONFIG_MEMFD_CREATE, is useful onits own even when not required by CONFIG_TMPFS or CONFIG_HUGETLBFS.Split it into its own proper bool option that can be enabled by users.Move that option into mm/ where the code itself also lies. Also add"select" statements to CONFIG_TMPFS and CONFIG_HUGETLBFS so theyautomatically enable CONFIG_MEMFD_CREATE as before.Link: https://lkml.kernel.org/r/20230630-config-memfd-v1-1-9acc3ae38b5a@weissschuh.netSigned-off-by: Thomas Weißschuh Tested-by: Zhangjin Wu Cc: Al Viro Cc: Christian Brauner Cc: Darrick J. Wong Signed-off-by: Andrew Morton List of files: /linux-6.15/fs/Kconfig