diff options
Diffstat (limited to '')
| -rw-r--r-- | fs/Kconfig | 399 | ||||
| -rw-r--r-- | fs/Kconfig.binfmt | 179 |
2 files changed, 578 insertions, 0 deletions
diff --git a/fs/Kconfig b/fs/Kconfig new file mode 100644 index 000000000..e99830c65 --- /dev/null +++ b/fs/Kconfig @@ -0,0 +1,399 @@ +# SPDX-License-Identifier: GPL-2.0-only +# +# File system configuration +# + +menu "File systems" + +# Use unaligned word dcache accesses +config DCACHE_WORD_ACCESS + bool + +config VALIDATE_FS_PARSER + bool "Validate filesystem parameter description" + help + Enable this to perform validation of the parameter description for a + filesystem when it is registered. + +config FS_IOMAP + bool + +# old blockdev_direct_IO implementation. Use iomap for new code instead +config LEGACY_DIRECT_IO + bool + +if BLOCK + +source "fs/ext2/Kconfig" +source "fs/ext4/Kconfig" +source "fs/jbd2/Kconfig" + +config FS_MBCACHE +# Meta block cache for Extended Attributes (ext2/ext3/ext4) + tristate + default y if EXT2_FS=y && EXT2_FS_XATTR + default y if EXT4_FS=y + default m if EXT2_FS_XATTR || EXT4_FS + +source "fs/reiserfs/Kconfig" +source "fs/jfs/Kconfig" + +source "fs/xfs/Kconfig" +source "fs/gfs2/Kconfig" +source "fs/ocfs2/Kconfig" +source "fs/btrfs/Kconfig" +source "fs/nilfs2/Kconfig" +source "fs/f2fs/Kconfig" +source "fs/zonefs/Kconfig" + +endif # BLOCK + +config FS_DAX + bool "File system based Direct Access (DAX) support" + depends on MMU + depends on !(ARM || MIPS || SPARC) + depends on ZONE_DEVICE || FS_DAX_LIMITED + select FS_IOMAP + select DAX + help + Direct Access (DAX) can be used on memory-backed block devices. + If the block device supports DAX and the filesystem supports DAX, + then you can avoid using the pagecache to buffer I/Os. Turning + on this option will compile in support for DAX. + + For a DAX device to support file system access it needs to have + struct pages. For the nfit based NVDIMMs this can be enabled + using the ndctl utility: + + # ndctl create-namespace --force --reconfig=namespace0.0 \ + --mode=fsdax --map=mem + + See the 'create-namespace' man page for details on the overhead of + --map=mem: + https://docs.pmem.io/ndctl-user-guide/ndctl-man-pages/ndctl-create-namespace + + For ndctl to work CONFIG_DEV_DAX needs to be enabled as well. For most + file systems DAX support needs to be manually enabled globally or + per-inode using a mount option as well. See the file documentation in + Documentation/filesystems/dax.rst for details. + + If you do not have a block device that is capable of using this, + or if unsure, say N. Saying Y will increase the size of the kernel + by about 5kB. + +config FS_DAX_PMD + bool + default FS_DAX + depends on FS_DAX + depends on ZONE_DEVICE + depends on TRANSPARENT_HUGEPAGE + +# Selected by DAX drivers that do not expect filesystem DAX to support +# get_user_pages() of DAX mappings. I.e. "limited" indicates no support +# for fork() of processes with MAP_SHARED mappings or support for +# direct-I/O to a DAX mapping. +config FS_DAX_LIMITED + bool + +# Posix ACL utility routines +# +# Note: Posix ACLs can be implemented without these helpers. Never use +# this symbol for ifdefs in core code. +# +config FS_POSIX_ACL + def_bool n + +config EXPORTFS + tristate + +config EXPORTFS_BLOCK_OPS + bool "Enable filesystem export operations for block IO" + help + This option enables the export operations for a filesystem to support + external block IO. + +config FILE_LOCKING + bool "Enable POSIX file locking API" if EXPERT + default y + help + This option enables standard file locking support, required + for filesystems like NFS and for the flock() system + call. Disabling this option saves about 11k. + +source "fs/crypto/Kconfig" + +source "fs/verity/Kconfig" + +source "fs/notify/Kconfig" + +source "fs/quota/Kconfig" + +source "fs/autofs/Kconfig" +source "fs/fuse/Kconfig" +source "fs/overlayfs/Kconfig" + +menu "Caches" + +source "fs/netfs/Kconfig" +source "fs/fscache/Kconfig" +source "fs/cachefiles/Kconfig" + +endmenu + +if BLOCK +menu "CD-ROM/DVD Filesystems" + +source "fs/isofs/Kconfig" +source "fs/udf/Kconfig" + +endmenu +endif # BLOCK + +if BLOCK +menu "DOS/FAT/EXFAT/NT Filesystems" + +source "fs/fat/Kconfig" +source "fs/exfat/Kconfig" +source "fs/ntfs/Kconfig" +source "fs/ntfs3/Kconfig" + +endmenu +endif # BLOCK + +menu "Pseudo filesystems" + +source "fs/proc/Kconfig" +source "fs/kernfs/Kconfig" +source "fs/sysfs/Kconfig" + +config TMPFS + bool "Tmpfs virtual memory file system support (former shm fs)" + depends on SHMEM + help + Tmpfs is a file system which keeps all files in virtual memory. + + Everything in tmpfs is temporary in the sense that no files will be + created on your hard drive. The files live in memory and swap + space. If you unmount a tmpfs instance, everything stored therein is + lost. + + See <file:Documentation/filesystems/tmpfs.rst> for details. + +config TMPFS_POSIX_ACL + bool "Tmpfs POSIX Access Control Lists" + depends on TMPFS + select TMPFS_XATTR + select FS_POSIX_ACL + help + POSIX Access Control Lists (ACLs) support additional access rights + for users and groups beyond the standard owner/group/world scheme, + and this option selects support for ACLs specifically for tmpfs + filesystems. + + If you've selected TMPFS, it's possible that you'll also need + this option as there are a number of Linux distros that require + POSIX ACL support under /dev for certain features to work properly. + For example, some distros need this feature for ALSA-related /dev + files for sound to work properly. In short, if you're not sure, + say Y. + +config TMPFS_XATTR + bool "Tmpfs extended attributes" + depends on TMPFS + default n + help + Extended attributes are name:value pairs associated with inodes by + the kernel or by users (see the attr(5) manual page for details). + + Currently this enables support for the trusted.* and + security.* namespaces. + + You need this for POSIX ACL support on tmpfs. + + If unsure, say N. + +config TMPFS_INODE64 + bool "Use 64-bit ino_t by default in tmpfs" + depends on TMPFS && 64BIT + default n + help + tmpfs has historically used only inode numbers as wide as an unsigned + int. In some cases this can cause wraparound, potentially resulting + in multiple files with the same inode number on a single device. This + option makes tmpfs use the full width of ino_t by default, without + needing to specify the inode64 option when mounting. + + But if a long-lived tmpfs is to be accessed by 32-bit applications so + ancient that opening a file larger than 2GiB fails with EINVAL, then + the INODE64 config option and inode64 mount option risk operations + failing with EOVERFLOW once 33-bit inode numbers are reached. + + To override this configured default, use the inode32 or inode64 + option when mounting. + + If unsure, say N. + +config ARCH_SUPPORTS_HUGETLBFS + def_bool n + +config HUGETLBFS + bool "HugeTLB file system support" + depends on X86 || IA64 || SPARC64 || ARCH_SUPPORTS_HUGETLBFS || BROKEN + depends on (SYSFS || SYSCTL) + help + hugetlbfs is a filesystem backing for HugeTLB pages, based on + ramfs. For architectures that support it, say Y here and read + <file:Documentation/admin-guide/mm/hugetlbpage.rst> for details. + + If unsure, say N. + +config HUGETLB_PAGE + def_bool HUGETLBFS + +# +# Select this config option from the architecture Kconfig, if it is preferred +# to enable the feature of HugeTLB Vmemmap Optimization (HVO). +# +config ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP + bool + +config HUGETLB_PAGE_OPTIMIZE_VMEMMAP + def_bool HUGETLB_PAGE + depends on ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP + depends on SPARSEMEM_VMEMMAP + +config HUGETLB_PAGE_OPTIMIZE_VMEMMAP_DEFAULT_ON + bool "HugeTLB Vmemmap Optimization (HVO) defaults to on" + default n + depends on HUGETLB_PAGE_OPTIMIZE_VMEMMAP + help + The HugeTLB VmemmapvOptimization (HVO) defaults to off. Say Y here to + enable HVO by default. It can be disabled via hugetlb_free_vmemmap=off + (boot command line) or hugetlb_optimize_vmemmap (sysctl). + +config MEMFD_CREATE + def_bool TMPFS || HUGETLBFS + +config ARCH_HAS_GIGANTIC_PAGE + bool + +source "fs/configfs/Kconfig" +source "fs/efivarfs/Kconfig" + +endmenu + +menuconfig MISC_FILESYSTEMS + bool "Miscellaneous filesystems" + default y + help + Say Y here to get to see options for various miscellaneous + filesystems, such as filesystems that came from other + operating systems. + + This option alone does not add any kernel code. + + If you say N, all options in this submenu will be skipped and + disabled; if unsure, say Y here. + +if MISC_FILESYSTEMS + +source "fs/orangefs/Kconfig" +source "fs/adfs/Kconfig" +source "fs/affs/Kconfig" +source "fs/ecryptfs/Kconfig" +source "fs/hfs/Kconfig" +source "fs/hfsplus/Kconfig" +source "fs/befs/Kconfig" +source "fs/bfs/Kconfig" +source "fs/efs/Kconfig" +source "fs/jffs2/Kconfig" +# UBIFS File system configuration +source "fs/ubifs/Kconfig" +source "fs/cramfs/Kconfig" +source "fs/squashfs/Kconfig" +source "fs/freevxfs/Kconfig" +source "fs/minix/Kconfig" +source "fs/omfs/Kconfig" +source "fs/hpfs/Kconfig" +source "fs/qnx4/Kconfig" +source "fs/qnx6/Kconfig" +source "fs/romfs/Kconfig" +source "fs/pstore/Kconfig" +source "fs/sysv/Kconfig" +source "fs/ufs/Kconfig" +source "fs/erofs/Kconfig" +source "fs/vboxsf/Kconfig" + +endif # MISC_FILESYSTEMS + +menuconfig NETWORK_FILESYSTEMS + bool "Network File Systems" + default y + depends on NET + help + Say Y here to get to see options for network filesystems and + filesystem-related networking code, such as NFS daemon and + RPCSEC security modules. + + This option alone does not add any kernel code. + + If you say N, all options in this submenu will be skipped and + disabled; if unsure, say Y here. + +if NETWORK_FILESYSTEMS + +source "fs/nfs/Kconfig" +source "fs/nfsd/Kconfig" + +config GRACE_PERIOD + tristate + +config LOCKD + tristate + depends on FILE_LOCKING + select GRACE_PERIOD + +config LOCKD_V4 + bool + depends on NFSD || NFS_V3 + depends on FILE_LOCKING + default y + +config NFS_ACL_SUPPORT + tristate + select FS_POSIX_ACL + +config NFS_COMMON + bool + depends on NFSD || NFS_FS || LOCKD + default y + +config NFS_V4_2_SSC_HELPER + bool + default y if NFS_V4_2 + +source "net/sunrpc/Kconfig" +source "fs/ceph/Kconfig" + +source "fs/cifs/Kconfig" +source "fs/ksmbd/Kconfig" + +config SMBFS_COMMON + tristate + default y if CIFS=y || SMB_SERVER=y + default m if CIFS=m || SMB_SERVER=m + +source "fs/coda/Kconfig" +source "fs/afs/Kconfig" +source "fs/9p/Kconfig" + +endif # NETWORK_FILESYSTEMS + +source "fs/nls/Kconfig" +source "fs/dlm/Kconfig" +source "fs/unicode/Kconfig" + +config IO_WQ + bool + +endmenu diff --git a/fs/Kconfig.binfmt b/fs/Kconfig.binfmt new file mode 100644 index 000000000..93539aac0 --- /dev/null +++ b/fs/Kconfig.binfmt @@ -0,0 +1,179 @@ +# SPDX-License-Identifier: GPL-2.0-only + +menu "Executable file formats" + +config BINFMT_ELF + bool "Kernel support for ELF binaries" + depends on MMU + select ELFCORE + default y + help + ELF (Executable and Linkable Format) is a format for libraries and + executables used across different architectures and operating + systems. Saying Y here will enable your kernel to run ELF binaries + and enlarge it by about 13 KB. ELF support under Linux has now all + but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC) + because it is portable (this does *not* mean that you will be able + to run executables from different architectures or operating systems + however) and makes building run-time libraries very easy. Many new + executables are distributed solely in ELF format. You definitely + want to say Y here. + + Information about ELF is contained in the ELF HOWTO available from + <http://www.tldp.org/docs.html#howto>. + + If you find that after upgrading from Linux kernel 1.2 and saying Y + here, you still can't run any ELF binaries (they just crash), then + you'll have to install the newest ELF runtime libraries, including + ld.so (check the file <file:Documentation/Changes> for location and + latest version). + +config BINFMT_ELF_KUNIT_TEST + bool "Build KUnit tests for ELF binary support" if !KUNIT_ALL_TESTS + depends on KUNIT=y && BINFMT_ELF=y + default KUNIT_ALL_TESTS + help + This builds the ELF loader KUnit tests, which try to gather + prior bug fixes into a regression test collection. This is really + only needed for debugging. Note that with CONFIG_COMPAT=y, the + compat_binfmt_elf KUnit test is also created. + +config COMPAT_BINFMT_ELF + def_bool y + depends on COMPAT && BINFMT_ELF + select ELFCORE + +config ARCH_BINFMT_ELF_STATE + bool + +config ARCH_BINFMT_ELF_EXTRA_PHDRS + bool + +config ARCH_HAVE_ELF_PROT + bool + +config ARCH_USE_GNU_PROPERTY + bool + +config BINFMT_ELF_FDPIC + bool "Kernel support for FDPIC ELF binaries" + default y if !BINFMT_ELF + depends on ARM || ((M68K || SUPERH || XTENSA) && !MMU) + select ELFCORE + help + ELF FDPIC binaries are based on ELF, but allow the individual load + segments of a binary to be located in memory independently of each + other. This makes this format ideal for use in environments where no + MMU is available as it still permits text segments to be shared, + even if data segments are not. + + It is also possible to run FDPIC ELF binaries on MMU linux also. + +config ELFCORE + bool + help + This option enables kernel/elfcore.o. + +config CORE_DUMP_DEFAULT_ELF_HEADERS + bool "Write ELF core dumps with partial segments" + default y + depends on BINFMT_ELF && ELF_CORE + help + ELF core dump files describe each memory mapping of the crashed + process, and can contain or omit the memory contents of each one. + The contents of an unmodified text mapping are omitted by default. + + For an unmodified text mapping of an ELF object, including just + the first page of the file in a core dump makes it possible to + identify the build ID bits in the file, without paying the i/o + cost and disk space to dump all the text. However, versions of + GDB before 6.7 are confused by ELF core dump files in this format. + + The core dump behavior can be controlled per process using + the /proc/PID/coredump_filter pseudo-file; this setting is + inherited. See Documentation/filesystems/proc.rst for details. + + This config option changes the default setting of coredump_filter + seen at boot time. If unsure, say Y. + +config BINFMT_SCRIPT + tristate "Kernel support for scripts starting with #!" + default y + help + Say Y here if you want to execute interpreted scripts starting with + #! followed by the path to an interpreter. + + You can build this support as a module; however, until that module + gets loaded, you cannot run scripts. Thus, if you want to load this + module from an initramfs, the portion of the initramfs before loading + this module must consist of compiled binaries only. + + Most systems will not boot if you say M or N here. If unsure, say Y. + +config ARCH_HAS_BINFMT_FLAT + bool + +config BINFMT_FLAT + bool "Kernel support for flat binaries" + depends on ARCH_HAS_BINFMT_FLAT + help + Support uClinux FLAT format binaries. + +config BINFMT_FLAT_ARGVP_ENVP_ON_STACK + bool + +config BINFMT_FLAT_OLD_ALWAYS_RAM + bool + +config BINFMT_FLAT_NO_DATA_START_OFFSET + bool + +config BINFMT_FLAT_OLD + bool "Enable support for very old legacy flat binaries" + depends on BINFMT_FLAT + help + Support decade old uClinux FLAT format binaries. Unless you know + you have some of those say N here. + +config BINFMT_ZFLAT + bool "Enable ZFLAT support" + depends on BINFMT_FLAT + select ZLIB_INFLATE + help + Support FLAT format compressed binaries + +config BINFMT_MISC + tristate "Kernel support for MISC binaries" + help + If you say Y here, it will be possible to plug wrapper-driven binary + formats into the kernel. You will like this especially when you use + programs that need an interpreter to run like Java, Python, .NET or + Emacs-Lisp. It's also useful if you often run DOS executables under + the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from + <http://www.tldp.org/docs.html#howto>). Once you have + registered such a binary class with the kernel, you can start one of + those programs simply by typing in its name at a shell prompt; Linux + will automatically feed it to the correct interpreter. + + You can do other nice things, too. Read the file + <file:Documentation/admin-guide/binfmt-misc.rst> to learn how to use this + feature, <file:Documentation/admin-guide/java.rst> for information about how + to include Java support. and <file:Documentation/admin-guide/mono.rst> for + information about how to include Mono-based .NET support. + + To use binfmt_misc, you will need to mount it: + mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc + + You may say M here for module support and later load the module when + you have use for it; the module is called binfmt_misc. If you + don't know what to answer at this point, say Y. + +config COREDUMP + bool "Enable core dump support" if EXPERT + default y + help + This option enables support for performing core dumps. You almost + certainly want to say Y here. Not necessary on systems that never + need debugging or only ever run flawless code. + +endmenu |