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>
Showing
- fs/cifs/inode.c 1 addition, 1 deletionfs/cifs/inode.c
- fs/ecryptfs/inode.c 1 addition, 2 deletionsfs/ecryptfs/inode.c
- fs/namei.c 13 additions, 19 deletionsfs/namei.c
- fs/nfsd/vfs.c 4 additions, 4 deletionsfs/nfsd/vfs.c
- fs/open.c 1 addition, 1 deletionfs/open.c
- fs/stat.c 1 addition, 1 deletionfs/stat.c
- fs/xattr.c 1 addition, 1 deletionfs/xattr.c
- mm/memory.c 2 additions, 2 deletionsmm/memory.c
- mm/nommu.c 1 addition, 1 deletionmm/nommu.c
- security/commoncap.c 3 additions, 3 deletionssecurity/commoncap.c
Loading
Please register or sign in to comment