1 # SPDX-License-Identifier: GPL-2.0-only << 2 config XFS_FS 1 config XFS_FS 3 tristate "XFS filesystem support" 2 tristate "XFS filesystem support" 4 depends on BLOCK 3 depends on BLOCK 5 select EXPORTFS 4 select EXPORTFS 6 select LIBCRC32C << 7 select FS_IOMAP << 8 help 5 help 9 XFS is a high performance journaling 6 XFS is a high performance journaling filesystem which originated 10 on the SGI IRIX platform. It is com 7 on the SGI IRIX platform. It is completely multi-threaded, can 11 support large files and large filesy 8 support large files and large filesystems, extended attributes, 12 variable block sizes, is extent base 9 variable block sizes, is extent based, and makes extensive use of 13 Btrees (directories, extents, free s 10 Btrees (directories, extents, free space) to aid both performance 14 and scalability. 11 and scalability. 15 12 16 Refer to the documentation at <http: 13 Refer to the documentation at <http://oss.sgi.com/projects/xfs/> 17 for complete details. This implemen 14 for complete details. This implementation is on-disk compatible 18 with the IRIX version of XFS. 15 with the IRIX version of XFS. 19 16 20 To compile this file system support 17 To compile this file system support as a module, choose M here: the 21 module will be called xfs. Be aware 18 module will be called xfs. Be aware, however, that if the file 22 system of your root partition is com 19 system of your root partition is compiled as a module, you'll need 23 to use an initial ramdisk (initrd) t 20 to use an initial ramdisk (initrd) to boot. 24 21 25 config XFS_SUPPORT_V4 << 26 bool "Support deprecated V4 (crc=0) fo << 27 depends on XFS_FS << 28 default y << 29 help << 30 The V4 filesystem format lacks certa << 31 by the V5 format, such as metadata c << 32 metadata verification, and the abili << 33 year 2038. Because of this, the V4 << 34 should upgrade by backing up their f << 35 from the backup. << 36 << 37 Administrators and users can detect << 38 xfs_info against a filesystem mountp << 39 beginning with "crc=". If the strin << 40 filesystem is a V4 filesystem. If n << 41 upgrade xfsprogs to the latest versi << 42 << 43 This option will become default N in << 44 V4 format will be removed entirely i << 45 can say N here to withdraw support e << 46 << 47 To continue supporting the old V4 fo << 48 To close off an attack surface, say << 49 << 50 config XFS_SUPPORT_ASCII_CI << 51 bool "Support deprecated case-insensit << 52 depends on XFS_FS << 53 default y << 54 help << 55 The ASCII case insensitivity filesys << 56 on systems that have been coerced in << 57 not work on extended attributes. Th << 58 the locale settings in userspace, so << 59 Enabling this feature makes XFS vuln << 60 attacks. Because of this, the featu << 61 should upgrade by backing up their f << 62 from the backup. << 63 << 64 Administrators and users can detect << 65 xfs_info against a filesystem mountp << 66 beginning with "ascii-ci=". If the << 67 filesystem is a case-insensitive fil << 68 found, please upgrade xfsprogs to th << 69 << 70 This option will become default N in << 71 feature will be removed entirely in << 72 can say N here to withdraw support e << 73 << 74 To continue supporting case-insensit << 75 To close off an attack surface, say << 76 << 77 config XFS_QUOTA 22 config XFS_QUOTA 78 bool "XFS Quota support" 23 bool "XFS Quota support" 79 depends on XFS_FS 24 depends on XFS_FS 80 select QUOTACTL << 81 help 25 help 82 If you say Y here, you will be able 26 If you say Y here, you will be able to set limits for disk usage on 83 a per user and/or a per group basis 27 a per user and/or a per group basis under XFS. XFS considers quota 84 information as filesystem metadata a 28 information as filesystem metadata and uses journaling to provide a 85 higher level guarantee of consistenc 29 higher level guarantee of consistency. The on-disk data format for 86 quota is also compatible with the IR 30 quota is also compatible with the IRIX version of XFS, allowing a 87 filesystem to be migrated between Li 31 filesystem to be migrated between Linux and IRIX without any need 88 for conversion. 32 for conversion. 89 33 90 If unsure, say N. More comprehensiv 34 If unsure, say N. More comprehensive documentation can be found in 91 README.quota in the xfsprogs package 35 README.quota in the xfsprogs package. XFS quota can be used either 92 with or without the generic quota su 36 with or without the generic quota support enabled (CONFIG_QUOTA) - 93 they are completely independent subs 37 they are completely independent subsystems. 94 38 95 config XFS_POSIX_ACL 39 config XFS_POSIX_ACL 96 bool "XFS POSIX ACL support" 40 bool "XFS POSIX ACL support" 97 depends on XFS_FS 41 depends on XFS_FS 98 select FS_POSIX_ACL 42 select FS_POSIX_ACL 99 help 43 help 100 POSIX Access Control Lists (ACLs) su 44 POSIX Access Control Lists (ACLs) support permissions for users and 101 groups beyond the owner/group/world 45 groups beyond the owner/group/world scheme. 102 46 >> 47 To learn more about Access Control Lists, visit the POSIX ACLs for >> 48 Linux website <http://acl.bestbits.at/>. >> 49 103 If you don't know what Access Contro 50 If you don't know what Access Control Lists are, say N. 104 51 105 config XFS_RT 52 config XFS_RT 106 bool "XFS Realtime subvolume support" 53 bool "XFS Realtime subvolume support" 107 depends on XFS_FS 54 depends on XFS_FS 108 help 55 help 109 If you say Y here you will be able t 56 If you say Y here you will be able to mount and use XFS filesystems 110 which contain a realtime subvolume. 57 which contain a realtime subvolume. The realtime subvolume is a 111 separate area of disk space where on 58 separate area of disk space where only file data is stored. It was 112 originally designed to provide deter 59 originally designed to provide deterministic data rates suitable 113 for media streaming applications, bu 60 for media streaming applications, but is also useful as a generic 114 mechanism for ensuring data and meta 61 mechanism for ensuring data and metadata/log I/Os are completely 115 separated. Regular file I/Os are is 62 separated. Regular file I/Os are isolated to a separate device 116 from all other requests, and this ca 63 from all other requests, and this can be done quite transparently 117 to applications via the inherit-real 64 to applications via the inherit-realtime directory inode flag. 118 65 119 See the xfs man page in section 5 fo 66 See the xfs man page in section 5 for additional information. 120 67 121 If unsure, say N. 68 If unsure, say N. 122 69 123 config XFS_DRAIN_INTENTS << 124 bool << 125 select JUMP_LABEL if HAVE_ARCH_JUMP_LA << 126 << 127 config XFS_LIVE_HOOKS << 128 bool << 129 select JUMP_LABEL if HAVE_ARCH_JUMP_LA << 130 << 131 config XFS_MEMORY_BUFS << 132 bool << 133 << 134 config XFS_BTREE_IN_MEM << 135 bool << 136 << 137 config XFS_ONLINE_SCRUB << 138 bool "XFS online metadata check suppor << 139 default n << 140 depends on XFS_FS << 141 depends on TMPFS && SHMEM << 142 select XFS_LIVE_HOOKS << 143 select XFS_DRAIN_INTENTS << 144 select XFS_MEMORY_BUFS << 145 help << 146 If you say Y here you will be able t << 147 mounted XFS filesystem. This featur << 148 filesystem downtime by supplementing << 149 advantage here is to look for proble << 150 they can be dealt with in a controll << 151 << 152 This feature is considered EXPERIMEN << 153 << 154 See the xfs_scrub man page in sectio << 155 << 156 If unsure, say N. << 157 << 158 config XFS_ONLINE_SCRUB_STATS << 159 bool "XFS online metadata check usage << 160 default y << 161 depends on XFS_ONLINE_SCRUB << 162 select DEBUG_FS << 163 help << 164 If you say Y here, the kernel will g << 165 the online metadata check subsystem. << 166 of invocations, the outcomes, and th << 167 This may slow down scrub slightly du << 168 timers and the need to merge per-inv << 169 filesystem counters. << 170 << 171 Usage data are collected in /sys/ker << 172 << 173 If unsure, say N. << 174 << 175 config XFS_ONLINE_REPAIR << 176 bool "XFS online metadata repair suppo << 177 default n << 178 depends on XFS_FS && XFS_ONLINE_SCRUB << 179 select XFS_BTREE_IN_MEM << 180 help << 181 If you say Y here you will be able t << 182 mounted XFS filesystem. This featur << 183 filesystem downtime by fixing minor << 184 filesystem to go down. However, it << 185 formatted with secondary metadata, s << 186 parent pointers. << 187 << 188 This feature is considered EXPERIMEN << 189 << 190 See the xfs_scrub man page in sectio << 191 << 192 If unsure, say N. << 193 << 194 config XFS_WARN << 195 bool "XFS Verbose Warnings" << 196 depends on XFS_FS && !XFS_DEBUG << 197 help << 198 Say Y here to get an XFS build with << 199 It converts ASSERT checks to WARN, s << 200 conditions that occur that would oth << 201 lighter weight than XFS_DEBUG and do << 202 not cause the kernel to panic on non << 203 << 204 However, similar to XFS_DEBUG, it is << 205 are debugging a particular problem. << 206 << 207 config XFS_DEBUG 70 config XFS_DEBUG 208 bool "XFS Debugging support" !! 71 bool "XFS Debugging support (EXPERIMENTAL)" 209 depends on XFS_FS !! 72 depends on XFS_FS && EXPERIMENTAL 210 help 73 help 211 Say Y here to get an XFS build with 74 Say Y here to get an XFS build with many debugging features, 212 including ASSERT checks, function wr 75 including ASSERT checks, function wrappers around macros, 213 and extra sanity-checking functions 76 and extra sanity-checking functions in various code paths. 214 77 215 Note that the resulting code will be 78 Note that the resulting code will be HUGE and SLOW, and probably 216 not useful unless you are debugging 79 not useful unless you are debugging a particular problem. 217 80 218 Say N unless you are an XFS develope 81 Say N unless you are an XFS developer, or you play one on TV. 219 << 220 config XFS_DEBUG_EXPENSIVE << 221 bool "XFS expensive debugging checks" << 222 depends on XFS_FS && XFS_DEBUG << 223 help << 224 Say Y here to get an XFS build with << 225 enabled. These checks may affect pe << 226 << 227 Note that the resulting code will be << 228 not useful unless you are debugging << 229 << 230 Say N unless you are an XFS develope << 231 << 232 config XFS_ASSERT_FATAL << 233 bool "XFS fatal asserts" << 234 default y << 235 depends on XFS_FS && XFS_DEBUG << 236 help << 237 Set the default DEBUG mode ASSERT fa << 238 << 239 Say Y here to cause DEBUG mode ASSER << 240 errors that BUG() the kernel by defa << 241 result in warnings. << 242 << 243 This behavior can be modified at run <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.