summaryrefslogtreecommitdiffstats
path: root/fs/squashfs/super.c
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2009-05-05 22:10:44 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2009-06-11 21:36:07 -0400
commita9e220f8322e2b0e0b8903fe00265461cffad3f0 (patch)
treeb3be7d58b8eb9fd810636223f0458191ec1b9d75 /fs/squashfs/super.c
parent62c6943b4b1e818aea60c11c5a68a50785b83119 (diff)
downloadop-kernel-dev-a9e220f8322e2b0e0b8903fe00265461cffad3f0.zip
op-kernel-dev-a9e220f8322e2b0e0b8903fe00265461cffad3f0.tar.gz
No need to do lock_super() for exclusion in generic_shutdown_super()
We can't run into contention on it. All other callers of lock_super() either hold s_umount (and we have it exclusive) or hold an active reference to superblock in question, which prevents the call of generic_shutdown_super() while the reference is held. So we can replace lock_super(s) with get_fs_excl() in generic_shutdown_super() (and corresponding change for unlock_super(), of course). Since ext4 expects s_lock held for its put_super, take lock_super() into it. The rest of filesystems do not care at all. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/squashfs/super.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud