Push lock_super() into the ->remount_fs() of filesystems that care about it
authorAl Viro <viro@zeniv.linux.org.uk>
Wed, 6 May 2009 14:43:07 +0000 (10:43 -0400)
committerAl Viro <viro@zeniv.linux.org.uk>
Fri, 12 Jun 2009 01:36:08 +0000 (21:36 -0400)
commitbbd6851a3213a525128473e978b692ab6ac11aba
tree8ebddebadd8992871ab98456187cb00849a82058
parent6cfd0148425e528b859b26e436b01f23f6926224
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>
fs/ext3/super.c
fs/ext4/super.c
fs/hpfs/super.c
fs/super.c
fs/sysv/inode.c
fs/ufs/super.c