939da10844
Ted has sent out a RFC about removing this feature. Eric and Jan confirmed that both RedHat and SUSE enable this feature in all their product. David also said that "As far as I know, it's enabled in all Android kernels that use ext4." So it seems OK for us. And what's more, as inline data depends its implementation on xattr, and to be frank, I don't run any test again inline data enabled while xattr disabled. So I think we should add inline data and remove this config option in the same release. [ The savings if you disable CONFIG_EXT4_FS_XATTR is only 27k, which isn't much in the grand scheme of things. Since no one seems to be testing this configuration except for some automated compile farms, on balance we are better removing this config option, and so that it is effectively always enabled. -- tytso ] Cc: David Brown <davidb@codeaurora.org> Cc: Eric Sandeen <sandeen@redhat.com> Reviewed-by: Jan Kara <jack@suse.cz> Signed-off-by: Tao Ma <boyu.mt@taobao.com> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
72 lines
2.5 KiB
Text
72 lines
2.5 KiB
Text
config EXT4_FS
|
|
tristate "The Extended 4 (ext4) filesystem"
|
|
select JBD2
|
|
select CRC16
|
|
select CRYPTO
|
|
select CRYPTO_CRC32C
|
|
help
|
|
This is the next generation of the ext3 filesystem.
|
|
|
|
Unlike the change from ext2 filesystem to ext3 filesystem,
|
|
the on-disk format of ext4 is not forwards compatible with
|
|
ext3; it is based on extent maps and it supports 48-bit
|
|
physical block numbers. The ext4 filesystem also supports delayed
|
|
allocation, persistent preallocation, high resolution time stamps,
|
|
and a number of other features to improve performance and speed
|
|
up fsck time. For more information, please see the web pages at
|
|
http://ext4.wiki.kernel.org.
|
|
|
|
The ext4 filesystem will support mounting an ext3
|
|
filesystem; while there will be some performance gains from
|
|
the delayed allocation and inode table readahead, the best
|
|
performance gains will require enabling ext4 features in the
|
|
filesystem, or formatting a new filesystem as an ext4
|
|
filesystem initially.
|
|
|
|
To compile this file system support as a module, choose M here. The
|
|
module will be called ext4.
|
|
|
|
If unsure, say N.
|
|
|
|
config EXT4_USE_FOR_EXT23
|
|
bool "Use ext4 for ext2/ext3 file systems"
|
|
depends on EXT4_FS
|
|
depends on EXT3_FS=n || EXT2_FS=n
|
|
default y
|
|
help
|
|
Allow the ext4 file system driver code to be used for ext2 or
|
|
ext3 file system mounts. This allows users to reduce their
|
|
compiled kernel size by using one file system driver for
|
|
ext2, ext3, and ext4 file systems.
|
|
|
|
config EXT4_FS_POSIX_ACL
|
|
bool "Ext4 POSIX Access Control Lists"
|
|
select FS_POSIX_ACL
|
|
help
|
|
POSIX Access Control Lists (ACLs) support permissions for users and
|
|
groups beyond the owner/group/world scheme.
|
|
|
|
To learn more about Access Control Lists, visit the POSIX ACLs for
|
|
Linux website <http://acl.bestbits.at/>.
|
|
|
|
If you don't know what Access Control Lists are, say N
|
|
|
|
config EXT4_FS_SECURITY
|
|
bool "Ext4 Security Labels"
|
|
help
|
|
Security labels support alternative access control models
|
|
implemented by security modules like SELinux. This option
|
|
enables an extended attribute handler for file security
|
|
labels in the ext4 filesystem.
|
|
|
|
If you are not using a security module that requires using
|
|
extended attributes for file security labels, say N.
|
|
|
|
config EXT4_DEBUG
|
|
bool "EXT4 debugging support"
|
|
depends on EXT4_FS
|
|
help
|
|
Enables run-time debugging support for the ext4 filesystem.
|
|
|
|
If you select Y here, then you will be able to turn on debugging
|
|
with a command such as "echo 1 > /sys/kernel/debug/ext4/mballoc-debug"
|