diff options
-rw-r--r-- | fs/Kconfig | 272 | ||||
-rw-r--r-- | fs/ext2/Kconfig | 55 | ||||
-rw-r--r-- | fs/ext3/Kconfig | 67 | ||||
-rw-r--r-- | fs/ext4/Kconfig | 79 | ||||
-rw-r--r-- | fs/jbd/Kconfig | 30 | ||||
-rw-r--r-- | fs/jbd2/Kconfig | 33 |
6 files changed, 269 insertions, 267 deletions
diff --git a/fs/Kconfig b/fs/Kconfig index 4eca61c201f0..e282002b94d2 100644 --- a/fs/Kconfig +++ b/fs/Kconfig | |||
@@ -6,61 +6,9 @@ menu "File systems" | |||
6 | 6 | ||
7 | if BLOCK | 7 | if BLOCK |
8 | 8 | ||
9 | config EXT2_FS | 9 | source "fs/ext2/Kconfig" |
10 | tristate "Second extended fs support" | 10 | source "fs/ext3/Kconfig" |
11 | help | 11 | source "fs/ext4/Kconfig" |
12 | Ext2 is a standard Linux file system for hard disks. | ||
13 | |||
14 | To compile this file system support as a module, choose M here: the | ||
15 | module will be called ext2. | ||
16 | |||
17 | If unsure, say Y. | ||
18 | |||
19 | config EXT2_FS_XATTR | ||
20 | bool "Ext2 extended attributes" | ||
21 | depends on EXT2_FS | ||
22 | help | ||
23 | Extended attributes are name:value pairs associated with inodes by | ||
24 | the kernel or by users (see the attr(5) manual page, or visit | ||
25 | <http://acl.bestbits.at/> for details). | ||
26 | |||
27 | If unsure, say N. | ||
28 | |||
29 | config EXT2_FS_POSIX_ACL | ||
30 | bool "Ext2 POSIX Access Control Lists" | ||
31 | depends on EXT2_FS_XATTR | ||
32 | select FS_POSIX_ACL | ||
33 | help | ||
34 | Posix Access Control Lists (ACLs) support permissions for users and | ||
35 | groups beyond the owner/group/world scheme. | ||
36 | |||
37 | To learn more about Access Control Lists, visit the Posix ACLs for | ||
38 | Linux website <http://acl.bestbits.at/>. | ||
39 | |||
40 | If you don't know what Access Control Lists are, say N | ||
41 | |||
42 | config EXT2_FS_SECURITY | ||
43 | bool "Ext2 Security Labels" | ||
44 | depends on EXT2_FS_XATTR | ||
45 | help | ||
46 | Security labels support alternative access control models | ||
47 | implemented by security modules like SELinux. This option | ||
48 | enables an extended attribute handler for file security | ||
49 | labels in the ext2 filesystem. | ||
50 | |||
51 | If you are not using a security module that requires using | ||
52 | extended attributes for file security labels, say N. | ||
53 | |||
54 | config EXT2_FS_XIP | ||
55 | bool "Ext2 execute in place support" | ||
56 | depends on EXT2_FS && MMU | ||
57 | help | ||
58 | Execute in place can be used on memory-backed block devices. If you | ||
59 | enable this option, you can select to mount block devices which are | ||
60 | capable of this feature without using the page cache. | ||
61 | |||
62 | If you do not use a block device that is capable of using this, | ||
63 | or if unsure, say N. | ||
64 | 12 | ||
65 | config FS_XIP | 13 | config FS_XIP |
66 | # execute in place | 14 | # execute in place |
@@ -68,218 +16,8 @@ config FS_XIP | |||
68 | depends on EXT2_FS_XIP | 16 | depends on EXT2_FS_XIP |
69 | default y | 17 | default y |
70 | 18 | ||
71 | config EXT3_FS | 19 | source "fs/jbd/Kconfig" |
72 | tristate "Ext3 journalling file system support" | 20 | source "fs/jbd2/Kconfig" |
73 | select JBD | ||
74 | help | ||
75 | This is the journalling version of the Second extended file system | ||
76 | (often called ext3), the de facto standard Linux file system | ||
77 | (method to organize files on a storage device) for hard disks. | ||
78 | |||
79 | The journalling code included in this driver means you do not have | ||
80 | to run e2fsck (file system checker) on your file systems after a | ||
81 | crash. The journal keeps track of any changes that were being made | ||
82 | at the time the system crashed, and can ensure that your file system | ||
83 | is consistent without the need for a lengthy check. | ||
84 | |||
85 | Other than adding the journal to the file system, the on-disk format | ||
86 | of ext3 is identical to ext2. It is possible to freely switch | ||
87 | between using the ext3 driver and the ext2 driver, as long as the | ||
88 | file system has been cleanly unmounted, or e2fsck is run on the file | ||
89 | system. | ||
90 | |||
91 | To add a journal on an existing ext2 file system or change the | ||
92 | behavior of ext3 file systems, you can use the tune2fs utility ("man | ||
93 | tune2fs"). To modify attributes of files and directories on ext3 | ||
94 | file systems, use chattr ("man chattr"). You need to be using | ||
95 | e2fsprogs version 1.20 or later in order to create ext3 journals | ||
96 | (available at <http://sourceforge.net/projects/e2fsprogs/>). | ||
97 | |||
98 | To compile this file system support as a module, choose M here: the | ||
99 | module will be called ext3. | ||
100 | |||
101 | config EXT3_FS_XATTR | ||
102 | bool "Ext3 extended attributes" | ||
103 | depends on EXT3_FS | ||
104 | default y | ||
105 | help | ||
106 | Extended attributes are name:value pairs associated with inodes by | ||
107 | the kernel or by users (see the attr(5) manual page, or visit | ||
108 | <http://acl.bestbits.at/> for details). | ||
109 | |||
110 | If unsure, say N. | ||
111 | |||
112 | You need this for POSIX ACL support on ext3. | ||
113 | |||
114 | config EXT3_FS_POSIX_ACL | ||
115 | bool "Ext3 POSIX Access Control Lists" | ||
116 | depends on EXT3_FS_XATTR | ||
117 | select FS_POSIX_ACL | ||
118 | help | ||
119 | Posix Access Control Lists (ACLs) support permissions for users and | ||
120 | groups beyond the owner/group/world scheme. | ||
121 | |||
122 | To learn more about Access Control Lists, visit the Posix ACLs for | ||
123 | Linux website <http://acl.bestbits.at/>. | ||
124 | |||
125 | If you don't know what Access Control Lists are, say N | ||
126 | |||
127 | config EXT3_FS_SECURITY | ||
128 | bool "Ext3 Security Labels" | ||
129 | depends on EXT3_FS_XATTR | ||
130 | help | ||
131 | Security labels support alternative access control models | ||
132 | implemented by security modules like SELinux. This option | ||
133 | enables an extended attribute handler for file security | ||
134 | labels in the ext3 filesystem. | ||
135 | |||
136 | If you are not using a security module that requires using | ||
137 | extended attributes for file security labels, say N. | ||
138 | |||
139 | config EXT4_FS | ||
140 | tristate "The Extended 4 (ext4) filesystem" | ||
141 | select JBD2 | ||
142 | select CRC16 | ||
143 | help | ||
144 | This is the next generation of the ext3 filesystem. | ||
145 | |||
146 | Unlike the change from ext2 filesystem to ext3 filesystem, | ||
147 | the on-disk format of ext4 is not forwards compatible with | ||
148 | ext3; it is based on extent maps and it supports 48-bit | ||
149 | physical block numbers. The ext4 filesystem also supports delayed | ||
150 | allocation, persistent preallocation, high resolution time stamps, | ||
151 | and a number of other features to improve performance and speed | ||
152 | up fsck time. For more information, please see the web pages at | ||
153 | http://ext4.wiki.kernel.org. | ||
154 | |||
155 | The ext4 filesystem will support mounting an ext3 | ||
156 | filesystem; while there will be some performance gains from | ||
157 | the delayed allocation and inode table readahead, the best | ||
158 | performance gains will require enabling ext4 features in the | ||
159 | filesystem, or formating a new filesystem as an ext4 | ||
160 | filesystem initially. | ||
161 | |||
162 | To compile this file system support as a module, choose M here. The | ||
163 | module will be called ext4. | ||
164 | |||
165 | If unsure, say N. | ||
166 | |||
167 | config EXT4DEV_COMPAT | ||
168 | bool "Enable ext4dev compatibility" | ||
169 | depends on EXT4_FS | ||
170 | help | ||
171 | Starting with 2.6.28, the name of the ext4 filesystem was | ||
172 | renamed from ext4dev to ext4. Unfortunately there are some | ||
173 | legacy userspace programs (such as klibc's fstype) have | ||
174 | "ext4dev" hardcoded. | ||
175 | |||
176 | To enable backwards compatibility so that systems that are | ||
177 | still expecting to mount ext4 filesystems using ext4dev, | ||
178 | chose Y here. This feature will go away by 2.6.31, so | ||
179 | please arrange to get your userspace programs fixed! | ||
180 | |||
181 | config EXT4_FS_XATTR | ||
182 | bool "Ext4 extended attributes" | ||
183 | depends on EXT4_FS | ||
184 | default y | ||
185 | help | ||
186 | Extended attributes are name:value pairs associated with inodes by | ||
187 | the kernel or by users (see the attr(5) manual page, or visit | ||
188 | <http://acl.bestbits.at/> for details). | ||
189 | |||
190 | If unsure, say N. | ||
191 | |||
192 | You need this for POSIX ACL support on ext4. | ||
193 | |||
194 | config EXT4_FS_POSIX_ACL | ||
195 | bool "Ext4 POSIX Access Control Lists" | ||
196 | depends on EXT4_FS_XATTR | ||
197 | select FS_POSIX_ACL | ||
198 | help | ||
199 | POSIX Access Control Lists (ACLs) support permissions for users and | ||
200 | groups beyond the owner/group/world scheme. | ||
201 | |||
202 | To learn more about Access Control Lists, visit the POSIX ACLs for | ||
203 | Linux website <http://acl.bestbits.at/>. | ||
204 | |||
205 | If you don't know what Access Control Lists are, say N | ||
206 | |||
207 | config EXT4_FS_SECURITY | ||
208 | bool "Ext4 Security Labels" | ||
209 | depends on EXT4_FS_XATTR | ||
210 | help | ||
211 | Security labels support alternative access control models | ||
212 | implemented by security modules like SELinux. This option | ||
213 | enables an extended attribute handler for file security | ||
214 | labels in the ext4 filesystem. | ||
215 | |||
216 | If you are not using a security module that requires using | ||
217 | extended attributes for file security labels, say N. | ||
218 | |||
219 | config JBD | ||
220 | tristate | ||
221 | help | ||
222 | This is a generic journalling layer for block devices. It is | ||
223 | currently used by the ext3 file system, but it could also be | ||
224 | used to add journal support to other file systems or block | ||
225 | devices such as RAID or LVM. | ||
226 | |||
227 | If you are using the ext3 file system, you need to say Y here. | ||
228 | If you are not using ext3 then you will probably want to say N. | ||
229 | |||
230 | To compile this device as a module, choose M here: the module will be | ||
231 | called jbd. If you are compiling ext3 into the kernel, you | ||
232 | cannot compile this code as a module. | ||
233 | |||
234 | config JBD_DEBUG | ||
235 | bool "JBD (ext3) debugging support" | ||
236 | depends on JBD && DEBUG_FS | ||
237 | help | ||
238 | If you are using the ext3 journaled file system (or potentially any | ||
239 | other file system/device using JBD), this option allows you to | ||
240 | enable debugging output while the system is running, in order to | ||
241 | help track down any problems you are having. By default the | ||
242 | debugging output will be turned off. | ||
243 | |||
244 | If you select Y here, then you will be able to turn on debugging | ||
245 | with "echo N > /sys/kernel/debug/jbd/jbd-debug", where N is a | ||
246 | number between 1 and 5, the higher the number, the more debugging | ||
247 | output is generated. To turn debugging off again, do | ||
248 | "echo 0 > /sys/kernel/debug/jbd/jbd-debug". | ||
249 | |||
250 | config JBD2 | ||
251 | tristate | ||
252 | select CRC32 | ||
253 | help | ||
254 | This is a generic journaling layer for block devices that support | ||
255 | both 32-bit and 64-bit block numbers. It is currently used by | ||
256 | the ext4 and OCFS2 filesystems, but it could also be used to add | ||
257 | journal support to other file systems or block devices such | ||
258 | as RAID or LVM. | ||
259 | |||
260 | If you are using ext4 or OCFS2, you need to say Y here. | ||
261 | If you are not using ext4 or OCFS2 then you will | ||
262 | probably want to say N. | ||
263 | |||
264 | To compile this device as a module, choose M here. The module will be | ||
265 | called jbd2. If you are compiling ext4 or OCFS2 into the kernel, | ||
266 | you cannot compile this code as a module. | ||
267 | |||
268 | config JBD2_DEBUG | ||
269 | bool "JBD2 (ext4) debugging support" | ||
270 | depends on JBD2 && DEBUG_FS | ||
271 | help | ||
272 | If you are using the ext4 journaled file system (or | ||
273 | potentially any other filesystem/device using JBD2), this option | ||
274 | allows you to enable debugging output while the system is running, | ||
275 | in order to help track down any problems you are having. | ||
276 | By default, the debugging output will be turned off. | ||
277 | |||
278 | If you select Y here, then you will be able to turn on debugging | ||
279 | with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a | ||
280 | number between 1 and 5. The higher the number, the more debugging | ||
281 | output is generated. To turn debugging off again, do | ||
282 | "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug". | ||
283 | 21 | ||
284 | config FS_MBCACHE | 22 | config FS_MBCACHE |
285 | # Meta block cache for Extended Attributes (ext2/ext3/ext4) | 23 | # Meta block cache for Extended Attributes (ext2/ext3/ext4) |
diff --git a/fs/ext2/Kconfig b/fs/ext2/Kconfig new file mode 100644 index 000000000000..14a6780fd034 --- /dev/null +++ b/fs/ext2/Kconfig | |||
@@ -0,0 +1,55 @@ | |||
1 | config EXT2_FS | ||
2 | tristate "Second extended fs support" | ||
3 | help | ||
4 | Ext2 is a standard Linux file system for hard disks. | ||
5 | |||
6 | To compile this file system support as a module, choose M here: the | ||
7 | module will be called ext2. | ||
8 | |||
9 | If unsure, say Y. | ||
10 | |||
11 | config EXT2_FS_XATTR | ||
12 | bool "Ext2 extended attributes" | ||
13 | depends on EXT2_FS | ||
14 | help | ||
15 | Extended attributes are name:value pairs associated with inodes by | ||
16 | the kernel or by users (see the attr(5) manual page, or visit | ||
17 | <http://acl.bestbits.at/> for details). | ||
18 | |||
19 | If unsure, say N. | ||
20 | |||
21 | config EXT2_FS_POSIX_ACL | ||
22 | bool "Ext2 POSIX Access Control Lists" | ||
23 | depends on EXT2_FS_XATTR | ||
24 | select FS_POSIX_ACL | ||
25 | help | ||
26 | Posix Access Control Lists (ACLs) support permissions for users and | ||
27 | groups beyond the owner/group/world scheme. | ||
28 | |||
29 | To learn more about Access Control Lists, visit the Posix ACLs for | ||
30 | Linux website <http://acl.bestbits.at/>. | ||
31 | |||
32 | If you don't know what Access Control Lists are, say N | ||
33 | |||
34 | config EXT2_FS_SECURITY | ||
35 | bool "Ext2 Security Labels" | ||
36 | depends on EXT2_FS_XATTR | ||
37 | help | ||
38 | Security labels support alternative access control models | ||
39 | implemented by security modules like SELinux. This option | ||
40 | enables an extended attribute handler for file security | ||
41 | labels in the ext2 filesystem. | ||
42 | |||
43 | If you are not using a security module that requires using | ||
44 | extended attributes for file security labels, say N. | ||
45 | |||
46 | config EXT2_FS_XIP | ||
47 | bool "Ext2 execute in place support" | ||
48 | depends on EXT2_FS && MMU | ||
49 | help | ||
50 | Execute in place can be used on memory-backed block devices. If you | ||
51 | enable this option, you can select to mount block devices which are | ||
52 | capable of this feature without using the page cache. | ||
53 | |||
54 | If you do not use a block device that is capable of using this, | ||
55 | or if unsure, say N. | ||
diff --git a/fs/ext3/Kconfig b/fs/ext3/Kconfig new file mode 100644 index 000000000000..8e0cfe44b0fc --- /dev/null +++ b/fs/ext3/Kconfig | |||
@@ -0,0 +1,67 @@ | |||
1 | config EXT3_FS | ||
2 | tristate "Ext3 journalling file system support" | ||
3 | select JBD | ||
4 | help | ||
5 | This is the journalling version of the Second extended file system | ||
6 | (often called ext3), the de facto standard Linux file system | ||
7 | (method to organize files on a storage device) for hard disks. | ||
8 | |||
9 | The journalling code included in this driver means you do not have | ||
10 | to run e2fsck (file system checker) on your file systems after a | ||
11 | crash. The journal keeps track of any changes that were being made | ||
12 | at the time the system crashed, and can ensure that your file system | ||
13 | is consistent without the need for a lengthy check. | ||
14 | |||
15 | Other than adding the journal to the file system, the on-disk format | ||
16 | of ext3 is identical to ext2. It is possible to freely switch | ||
17 | between using the ext3 driver and the ext2 driver, as long as the | ||
18 | file system has been cleanly unmounted, or e2fsck is run on the file | ||
19 | system. | ||
20 | |||
21 | To add a journal on an existing ext2 file system or change the | ||
22 | behavior of ext3 file systems, you can use the tune2fs utility ("man | ||
23 | tune2fs"). To modify attributes of files and directories on ext3 | ||
24 | file systems, use chattr ("man chattr"). You need to be using | ||
25 | e2fsprogs version 1.20 or later in order to create ext3 journals | ||
26 | (available at <http://sourceforge.net/projects/e2fsprogs/>). | ||
27 | |||
28 | To compile this file system support as a module, choose M here: the | ||
29 | module will be called ext3. | ||
30 | |||
31 | config EXT3_FS_XATTR | ||
32 | bool "Ext3 extended attributes" | ||
33 | depends on EXT3_FS | ||
34 | default y | ||
35 | help | ||
36 | Extended attributes are name:value pairs associated with inodes by | ||
37 | the kernel or by users (see the attr(5) manual page, or visit | ||
38 | <http://acl.bestbits.at/> for details). | ||
39 | |||
40 | If unsure, say N. | ||
41 | |||
42 | You need this for POSIX ACL support on ext3. | ||
43 | |||
44 | config EXT3_FS_POSIX_ACL | ||
45 | bool "Ext3 POSIX Access Control Lists" | ||
46 | depends on EXT3_FS_XATTR | ||
47 | select FS_POSIX_ACL | ||
48 | help | ||
49 | Posix Access Control Lists (ACLs) support permissions for users and | ||
50 | groups beyond the owner/group/world scheme. | ||
51 | |||
52 | To learn more about Access Control Lists, visit the Posix ACLs for | ||
53 | Linux website <http://acl.bestbits.at/>. | ||
54 | |||
55 | If you don't know what Access Control Lists are, say N | ||
56 | |||
57 | config EXT3_FS_SECURITY | ||
58 | bool "Ext3 Security Labels" | ||
59 | depends on EXT3_FS_XATTR | ||
60 | help | ||
61 | Security labels support alternative access control models | ||
62 | implemented by security modules like SELinux. This option | ||
63 | enables an extended attribute handler for file security | ||
64 | labels in the ext3 filesystem. | ||
65 | |||
66 | If you are not using a security module that requires using | ||
67 | extended attributes for file security labels, say N. | ||
diff --git a/fs/ext4/Kconfig b/fs/ext4/Kconfig new file mode 100644 index 000000000000..7505482a08fa --- /dev/null +++ b/fs/ext4/Kconfig | |||
@@ -0,0 +1,79 @@ | |||
1 | config EXT4_FS | ||
2 | tristate "The Extended 4 (ext4) filesystem" | ||
3 | select JBD2 | ||
4 | select CRC16 | ||
5 | help | ||
6 | This is the next generation of the ext3 filesystem. | ||
7 | |||
8 | Unlike the change from ext2 filesystem to ext3 filesystem, | ||
9 | the on-disk format of ext4 is not forwards compatible with | ||
10 | ext3; it is based on extent maps and it supports 48-bit | ||
11 | physical block numbers. The ext4 filesystem also supports delayed | ||
12 | allocation, persistent preallocation, high resolution time stamps, | ||
13 | and a number of other features to improve performance and speed | ||
14 | up fsck time. For more information, please see the web pages at | ||
15 | http://ext4.wiki.kernel.org. | ||
16 | |||
17 | The ext4 filesystem will support mounting an ext3 | ||
18 | filesystem; while there will be some performance gains from | ||
19 | the delayed allocation and inode table readahead, the best | ||
20 | performance gains will require enabling ext4 features in the | ||
21 | filesystem, or formating a new filesystem as an ext4 | ||
22 | filesystem initially. | ||
23 | |||
24 | To compile this file system support as a module, choose M here. The | ||
25 | module will be called ext4. | ||
26 | |||
27 | If unsure, say N. | ||
28 | |||
29 | config EXT4DEV_COMPAT | ||
30 | bool "Enable ext4dev compatibility" | ||
31 | depends on EXT4_FS | ||
32 | help | ||
33 | Starting with 2.6.28, the name of the ext4 filesystem was | ||
34 | renamed from ext4dev to ext4. Unfortunately there are some | ||
35 | legacy userspace programs (such as klibc's fstype) have | ||
36 | "ext4dev" hardcoded. | ||
37 | |||
38 | To enable backwards compatibility so that systems that are | ||
39 | still expecting to mount ext4 filesystems using ext4dev, | ||
40 | chose Y here. This feature will go away by 2.6.31, so | ||
41 | please arrange to get your userspace programs fixed! | ||
42 | |||
43 | config EXT4_FS_XATTR | ||
44 | bool "Ext4 extended attributes" | ||
45 | depends on EXT4_FS | ||
46 | default y | ||
47 | help | ||
48 | Extended attributes are name:value pairs associated with inodes by | ||
49 | the kernel or by users (see the attr(5) manual page, or visit | ||
50 | <http://acl.bestbits.at/> for details). | ||
51 | |||
52 | If unsure, say N. | ||
53 | |||
54 | You need this for POSIX ACL support on ext4. | ||
55 | |||
56 | config EXT4_FS_POSIX_ACL | ||
57 | bool "Ext4 POSIX Access Control Lists" | ||
58 | depends on EXT4_FS_XATTR | ||
59 | select FS_POSIX_ACL | ||
60 | help | ||
61 | POSIX Access Control Lists (ACLs) support permissions for users and | ||
62 | groups beyond the owner/group/world scheme. | ||
63 | |||
64 | To learn more about Access Control Lists, visit the POSIX ACLs for | ||
65 | Linux website <http://acl.bestbits.at/>. | ||
66 | |||
67 | If you don't know what Access Control Lists are, say N | ||
68 | |||
69 | config EXT4_FS_SECURITY | ||
70 | bool "Ext4 Security Labels" | ||
71 | depends on EXT4_FS_XATTR | ||
72 | help | ||
73 | Security labels support alternative access control models | ||
74 | implemented by security modules like SELinux. This option | ||
75 | enables an extended attribute handler for file security | ||
76 | labels in the ext4 filesystem. | ||
77 | |||
78 | If you are not using a security module that requires using | ||
79 | extended attributes for file security labels, say N. | ||
diff --git a/fs/jbd/Kconfig b/fs/jbd/Kconfig new file mode 100644 index 000000000000..4e28beeed157 --- /dev/null +++ b/fs/jbd/Kconfig | |||
@@ -0,0 +1,30 @@ | |||
1 | config JBD | ||
2 | tristate | ||
3 | help | ||
4 | This is a generic journalling layer for block devices. It is | ||
5 | currently used by the ext3 file system, but it could also be | ||
6 | used to add journal support to other file systems or block | ||
7 | devices such as RAID or LVM. | ||
8 | |||
9 | If you are using the ext3 file system, you need to say Y here. | ||
10 | If you are not using ext3 then you will probably want to say N. | ||
11 | |||
12 | To compile this device as a module, choose M here: the module will be | ||
13 | called jbd. If you are compiling ext3 into the kernel, you | ||
14 | cannot compile this code as a module. | ||
15 | |||
16 | config JBD_DEBUG | ||
17 | bool "JBD (ext3) debugging support" | ||
18 | depends on JBD && DEBUG_FS | ||
19 | help | ||
20 | If you are using the ext3 journaled file system (or potentially any | ||
21 | other file system/device using JBD), this option allows you to | ||
22 | enable debugging output while the system is running, in order to | ||
23 | help track down any problems you are having. By default the | ||
24 | debugging output will be turned off. | ||
25 | |||
26 | If you select Y here, then you will be able to turn on debugging | ||
27 | with "echo N > /sys/kernel/debug/jbd/jbd-debug", where N is a | ||
28 | number between 1 and 5, the higher the number, the more debugging | ||
29 | output is generated. To turn debugging off again, do | ||
30 | "echo 0 > /sys/kernel/debug/jbd/jbd-debug". | ||
diff --git a/fs/jbd2/Kconfig b/fs/jbd2/Kconfig new file mode 100644 index 000000000000..f32f346f4b0a --- /dev/null +++ b/fs/jbd2/Kconfig | |||
@@ -0,0 +1,33 @@ | |||
1 | config JBD2 | ||
2 | tristate | ||
3 | select CRC32 | ||
4 | help | ||
5 | This is a generic journaling layer for block devices that support | ||
6 | both 32-bit and 64-bit block numbers. It is currently used by | ||
7 | the ext4 and OCFS2 filesystems, but it could also be used to add | ||
8 | journal support to other file systems or block devices such | ||
9 | as RAID or LVM. | ||
10 | |||
11 | If you are using ext4 or OCFS2, you need to say Y here. | ||
12 | If you are not using ext4 or OCFS2 then you will | ||
13 | probably want to say N. | ||
14 | |||
15 | To compile this device as a module, choose M here. The module will be | ||
16 | called jbd2. If you are compiling ext4 or OCFS2 into the kernel, | ||
17 | you cannot compile this code as a module. | ||
18 | |||
19 | config JBD2_DEBUG | ||
20 | bool "JBD2 (ext4) debugging support" | ||
21 | depends on JBD2 && DEBUG_FS | ||
22 | help | ||
23 | If you are using the ext4 journaled file system (or | ||
24 | potentially any other filesystem/device using JBD2), this option | ||
25 | allows you to enable debugging output while the system is running, | ||
26 | in order to help track down any problems you are having. | ||
27 | By default, the debugging output will be turned off. | ||
28 | |||
29 | If you select Y here, then you will be able to turn on debugging | ||
30 | with "echo N > /sys/kernel/debug/jbd2/jbd2-debug", where N is a | ||
31 | number between 1 and 5. The higher the number, the more debugging | ||
32 | output is generated. To turn debugging off again, do | ||
33 | "echo 0 > /sys/kernel/debug/jbd2/jbd2-debug". | ||