remarkable-linux/fs/ufs
Al Viro bbd6851a32 Push lock_super() into the ->remount_fs() of filesystems that care about it
Note that since we can't run into contention between remount_fs and write_super
(due to exclusion on s_umount), we have to care only about filesystems that
touch lock_super() on their own.  Out of those ext3, ext4, hpfs, sysv and ufs
do need it; fat doesn't since its ->remount_fs() only accesses assign-once
data (basically, it's "we have no atime on directories and only have atime on
files for vfat; force nodiratime and possibly noatime into *flags").

[folded a build fix from hch]

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2009-06-11 21:36:08 -04:00
..
balloc.c
cylinder.c
dir.c switch ufs directories to ufs_sync_file() 2009-05-09 10:49:42 -04:00
file.c switch ufs directories to ufs_sync_file() 2009-05-09 10:49:42 -04:00
ialloc.c
inode.c ufs: ensure fast symlinks are NUL-terminated 2009-03-27 14:43:58 -04:00
Kconfig
Makefile
namei.c ufs: copy symlink data into the correct union member 2009-03-27 14:43:58 -04:00
super.c Push lock_super() into the ->remount_fs() of filesystems that care about it 2009-06-11 21:36:08 -04:00
swab.h
symlink.c
truncate.c
ufs.h switch ufs directories to ufs_sync_file() 2009-05-09 10:49:42 -04:00
ufs_fs.h
util.c
util.h