.. | .. |
---|
| 1 | +# SPDX-License-Identifier: GPL-2.0-only |
---|
1 | 2 | # Ext3 configs are here for backward compatibility with old configs which may |
---|
2 | 3 | # have EXT3_FS set but not EXT4_FS set and thus would result in non-bootable |
---|
3 | 4 | # kernels after the removal of ext3 driver. |
---|
4 | 5 | config EXT3_FS |
---|
5 | 6 | tristate "The Extended 3 (ext3) filesystem" |
---|
6 | | - # These must match EXT4_FS selects... |
---|
7 | 7 | select EXT4_FS |
---|
8 | | - select JBD2 |
---|
9 | | - select CRC16 |
---|
10 | | - select CRYPTO |
---|
11 | | - select CRYPTO_CRC32C |
---|
12 | 8 | help |
---|
13 | 9 | This config option is here only for backward compatibility. ext3 |
---|
14 | 10 | filesystem is now handled by the ext4 driver. |
---|
.. | .. |
---|
32 | 28 | |
---|
33 | 29 | config EXT4_FS |
---|
34 | 30 | tristate "The Extended 4 (ext4) filesystem" |
---|
35 | | - # Please update EXT3_FS selects when changing these |
---|
36 | 31 | select JBD2 |
---|
37 | 32 | select CRC16 |
---|
38 | 33 | select CRYPTO |
---|
.. | .. |
---|
97 | 92 | If you are not using a security module that requires using |
---|
98 | 93 | extended attributes for file security labels, say N. |
---|
99 | 94 | |
---|
100 | | -config EXT4_ENCRYPTION |
---|
101 | | - bool "Ext4 Encryption" |
---|
102 | | - depends on EXT4_FS |
---|
103 | | - select FS_ENCRYPTION |
---|
104 | | - help |
---|
105 | | - This kconfig symbol is deprecated; now it just selects |
---|
106 | | - FS_ENCRYPTION. Use CONFIG_FS_ENCRYPTION=y in new config |
---|
107 | | - files |
---|
108 | | - |
---|
109 | | -config EXT4_FS_ENCRYPTION |
---|
110 | | - bool |
---|
111 | | - default y |
---|
112 | | - depends on EXT4_ENCRYPTION |
---|
113 | | - |
---|
114 | 95 | config EXT4_DEBUG |
---|
115 | | - bool "EXT4 debugging support" |
---|
| 96 | + bool "Ext4 debugging support" |
---|
116 | 97 | depends on EXT4_FS |
---|
117 | 98 | help |
---|
118 | 99 | Enables run-time debugging support for the ext4 filesystem. |
---|
119 | 100 | |
---|
120 | 101 | If you select Y here, then you will be able to turn on debugging |
---|
121 | | - with a command such as: |
---|
122 | | - echo 1 > /sys/module/ext4/parameters/mballoc_debug |
---|
| 102 | + using dynamic debug control for mb_debug() / ext_debug() msgs. |
---|
| 103 | + |
---|
| 104 | +config EXT4_KUNIT_TESTS |
---|
| 105 | + tristate "KUnit tests for ext4" if !KUNIT_ALL_TESTS |
---|
| 106 | + depends on EXT4_FS && KUNIT |
---|
| 107 | + default KUNIT_ALL_TESTS |
---|
| 108 | + help |
---|
| 109 | + This builds the ext4 KUnit tests. |
---|
| 110 | + |
---|
| 111 | + KUnit tests run during boot and output the results to the debug log |
---|
| 112 | + in TAP format (https://testanything.org/). Only useful for kernel devs |
---|
| 113 | + running KUnit test harness and are not for inclusion into a production |
---|
| 114 | + build. |
---|
| 115 | + |
---|
| 116 | + For more information on KUnit and unit tests in general please refer |
---|
| 117 | + to the KUnit documentation in Documentation/dev-tools/kunit/. |
---|
| 118 | + |
---|
| 119 | + If unsure, say N. |
---|