kernel-ark/fs/ext4
Theodore Tso 469108ff3d ext4: Add new "development flag" to the ext4 filesystem
This flag is simply a generic "this is a crash/burn test filesystem"
marker.  If it is set, then filesystem code which is "in development"
will be allowed to mount the filesystem.  Filesystem code which is not
considered ready for prime-time will check for this flag, and if it is
not set, it will refuse to touch the filesystem.

As we start rolling ext4 out to distro's like Fedora, et. al, this makes
it less likely that a user might accidentally start using ext4 on a
production filesystem; a bad thing, since that will essentially make it
be unfsckable until e2fsprogs catches up.

Signed-off-by: Theodore Tso <tytso@MIT.EDU>
Signed-off-by: Mingming Cao <cmm@us.ibm.com>
2008-02-10 01:11:44 -05:00
..
acl.c
acl.h
balloc.c
bitmap.c
dir.c
ext4_jbd2.c
extents.c
file.c
fsync.c
group.h
hash.c
ialloc.c
inode.c ext4: Fix Direct I/O locking 2008-02-10 01:08:38 -05:00
ioctl.c
Makefile
mballoc.c ext4: allocate struct ext4_allocation_context from a kmem cache 2008-02-10 01:13:33 -05:00
migrate.c ext4: Fix circular locking dependency with migrate and rm. 2008-02-10 01:20:05 -05:00
namei.c
namei.h
resize.c
super.c ext4: Add new "development flag" to the ext4 filesystem 2008-02-10 01:11:44 -05:00
symlink.c
xattr_security.c
xattr_trusted.c
xattr_user.c
xattr.c
xattr.h