diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2009-05-06 16:43:07 +0200 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2009-06-12 03:36:08 +0200 |
| commit | bbd6851a3213a525128473e978b692ab6ac11aba (patch) | |
| tree | 8ebddebadd8992871ab98456187cb00849a82058 /security | |
| parent | push BKL down into ->put_super (diff) | |
| download | linux-bbd6851a3213a525128473e978b692ab6ac11aba.tar.xz linux-bbd6851a3213a525128473e978b692ab6ac11aba.zip | |
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>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions