linux/fs/sysv
Linus Torvalds da53be12bb Don't pass inode to ->d_hash() and ->d_compare()
Instances either don't look at it at all (the majority of cases) or
only want it to find the superblock (which can be had as dentry->d_sb).
A few cases that want more are actually safe with dentry->d_inode -
the only precaution needed is the check that it hadn't been replaced with
NULL by rmdir() or by overwriting rename(), which case should be simply
treated as cache miss.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2013-06-29 12:57:36 +04:00
..
balloc.c sysv: drop lock/unlock super 2012-10-09 23:33:39 -04:00
dir.c [readdir] simple local unixlike: switch to ->iterate() 2013-06-29 12:46:47 +04:00
file.c sysv: drop vmtruncate 2012-12-20 14:00:01 -05:00
ialloc.c sysv: drop lock/unlock super 2012-10-09 23:33:39 -04:00
inode.c sysv: drop lock/unlock super 2012-10-09 23:33:39 -04:00
itree.c sysv: drop vmtruncate 2012-12-20 14:00:01 -05:00
Kconfig
Makefile
namei.c Don't pass inode to ->d_hash() and ->d_compare() 2013-06-29 12:57:36 +04:00
super.c fs: Readd the fs module aliases. 2013-03-12 18:55:21 -07:00
symlink.c
sysv.h sysv: drop lock/unlock super 2012-10-09 23:33:39 -04:00