xref: /openbmc/linux/fs/btrfs/Kconfig (revision 861e10be)
1config BTRFS_FS
2	tristate "Btrfs filesystem (EXPERIMENTAL) Unstable disk format"
3	depends on EXPERIMENTAL
4	select LIBCRC32C
5	select ZLIB_INFLATE
6	select ZLIB_DEFLATE
7	select LZO_COMPRESS
8	select LZO_DECOMPRESS
9	help
10	  Btrfs is a new filesystem with extents, writable snapshotting,
11	  support for multiple devices and many more features.
12
13	  Btrfs is highly experimental, and THE DISK FORMAT IS NOT YET
14	  FINALIZED.  You should say N here unless you are interested in
15	  testing Btrfs with non-critical data.
16
17	  To compile this file system support as a module, choose M here. The
18	  module will be called btrfs.
19
20	  If unsure, say N.
21
22config BTRFS_FS_POSIX_ACL
23	bool "Btrfs POSIX Access Control Lists"
24	depends on BTRFS_FS
25	select FS_POSIX_ACL
26	help
27	  POSIX Access Control Lists (ACLs) support permissions for users and
28	  groups beyond the owner/group/world scheme.
29
30	  To learn more about Access Control Lists, visit the POSIX ACLs for
31	  Linux website <http://acl.bestbits.at/>.
32
33	  If you don't know what Access Control Lists are, say N
34
35config BTRFS_FS_CHECK_INTEGRITY
36	bool "Btrfs with integrity check tool compiled in (DANGEROUS)"
37	depends on BTRFS_FS
38	help
39	  Adds code that examines all block write requests (including
40	  writes of the super block). The goal is to verify that the
41	  state of the filesystem on disk is always consistent, i.e.,
42	  after a power-loss or kernel panic event the filesystem is
43	  in a consistent state.
44
45	  If the integrity check tool is included and activated in
46	  the mount options, plenty of kernel memory is used, and
47	  plenty of additional CPU cycles are spent. Enabling this
48	  functionality is not intended for normal use.
49
50	  In most cases, unless you are a btrfs developer who needs
51	  to verify the integrity of (super)-block write requests
52	  during the run of a regression test, say N
53