tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1# SPDX-License-Identifier: GPL-2.0
2
3config BTRFS_FS
4 tristate "Btrfs filesystem support"
5 select BLK_CGROUP_PUNT_BIO
6 select CRC32
7 select CRYPTO
8 select CRYPTO_CRC32C
9 select CRYPTO_XXHASH
10 select CRYPTO_SHA256
11 select CRYPTO_BLAKE2B
12 select ZLIB_INFLATE
13 select ZLIB_DEFLATE
14 select LZO_COMPRESS
15 select LZO_DECOMPRESS
16 select ZSTD_COMPRESS
17 select ZSTD_DECOMPRESS
18 select FS_IOMAP
19 select RAID6_PQ
20 select XOR_BLOCKS
21 depends on PAGE_SIZE_LESS_THAN_256KB
22
23 help
24 Btrfs is a general purpose copy-on-write filesystem with extents,
25 writable snapshotting, support for multiple devices and many more
26 features focused on fault tolerance, repair and easy administration.
27
28 The filesystem disk format is no longer unstable, and it's not
29 expected to change unless there are strong reasons to do so. If there
30 is a format change, file systems with a unchanged format will
31 continue to be mountable and usable by newer kernels.
32
33 For more information, please see the web pages at
34 https://btrfs.readthedocs.io
35
36 To compile this file system support as a module, choose M here. The
37 module will be called btrfs.
38
39 If unsure, say N.
40
41config BTRFS_FS_POSIX_ACL
42 bool "Btrfs POSIX Access Control Lists"
43 depends on BTRFS_FS
44 select FS_POSIX_ACL
45 help
46 POSIX Access Control Lists (ACLs) support permissions for users and
47 groups beyond the owner/group/world scheme.
48
49 If you don't know what Access Control Lists are, say N
50
51config BTRFS_FS_RUN_SANITY_TESTS
52 bool "Btrfs will run sanity tests upon loading"
53 depends on BTRFS_FS
54 help
55 This will run sanity tests for core functionality like free space,
56 extent maps, extent io, extent buffers, inodes, qgroups and others,
57 at module load time. These are mostly regression tests and are only
58 interesting to developers.
59
60 If unsure, say N.
61
62config BTRFS_DEBUG
63 bool "Btrfs debugging support"
64 depends on BTRFS_FS
65 help
66 Enable run-time debugging support for the btrfs filesystem.
67
68 Additional potentially expensive checks, debugging functionality or
69 sysfs exported information is enabled, like leak checks of internal
70 objects, optional forced space fragmentation and /sys/fs/btrfs/debug .
71 This has negative impact on performance.
72
73 If unsure, say N.
74
75config BTRFS_ASSERT
76 bool "Btrfs assert support"
77 depends on BTRFS_FS
78 help
79 Enable run-time assertion checking. Additional safety checks are
80 done, simple enough not to affect performance but verify invariants
81 and assumptions of code to run properly. This may result in panics,
82 and is meant for developers but can be enabled in general.
83
84 If unsure, say N.
85
86config BTRFS_EXPERIMENTAL
87 bool "Btrfs experimental features"
88 depends on BTRFS_FS
89 default n
90 help
91 Enable experimental features. These features may not be stable enough
92 for end users. This is meant for btrfs developers or users who wish
93 to test the functionality and report problems.
94
95 Current list:
96
97 - COW fixup worker warning - last warning before removing the
98 functionality catching out-of-band page
99 dirtying, not necessary since 5.8
100
101 - RAID mirror read policy - additional read policies for balancing
102 reading from redundant block group
103 profiles (currently: pid, round-robin,
104 fixed devid)
105
106 - send stream protocol v3 - fs-verity support
107
108 - checksum offload mode - sysfs knob to affect when checksums are
109 calculated (at IO time, or in a thread)
110
111 - raid-stripe-tree - additional mapping of extents to devices to
112 support RAID1* profiles on zoned devices,
113 RAID56 not yet supported
114
115 - extent tree v2 - complex rework of extent tracking
116
117 - large folio support
118
119 If unsure, say N.
120
121config BTRFS_FS_REF_VERIFY
122 bool "Btrfs with the ref verify tool compiled in"
123 depends on BTRFS_FS
124 default n
125 help
126 Enable run-time extent reference verification instrumentation. This
127 is meant to be used by btrfs developers for tracking down extent
128 reference problems or verifying they didn't break something.
129
130 If unsure, say N.