inode->i_op is never NULL
authorAl Viro <viro@zeniv.linux.org.uk>
Thu, 4 Dec 2008 15:06:33 +0000 (10:06 -0500)
committerAl Viro <viro@zeniv.linux.org.uk>
Mon, 5 Jan 2009 16:54:28 +0000 (11:54 -0500)
commitacfa4380efe77e290d3a96b11cd4c9f24f4fbb18
treed656232c7ef39c83681c2de4c8e28ba439242f66
parent9742df331deb3fce95b321f38d4ea0c4e75edb63
inode->i_op is never NULL

We used to have rather schizophrenic set of checks for NULL ->i_op even
though it had been eliminated years ago.  You'd need to go out of your
way to set it to NULL explicitly _and_ a bunch of code would die on
such inodes anyway.  After killing two remaining places that still
did that bogosity, all that crap can go away.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fs/cifs/inode.c
fs/ecryptfs/inode.c
fs/namei.c
fs/nfsd/vfs.c
fs/open.c
fs/stat.c
fs/xattr.c
mm/memory.c
mm/nommu.c
security/commoncap.c