vfs: fix the stupidity with i_dentry in inode destructors
Seeing that just about every destructor got that INIT_LIST_HEAD() copied into
it, there is no point whatsoever keeping this INIT_LIST_HEAD in inode_init_once();
the cost of taking it into inode_init_always() will be negligible for pipes
and sockets and negative for everything else. Not to mention the removal of
boilerplate code from ->destroy_inode() instances...
Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk>
Showing
- arch/powerpc/platforms/cell/spufs/inode.c 0 additions, 1 deletionarch/powerpc/platforms/cell/spufs/inode.c
- drivers/staging/pohmelfs/inode.c 0 additions, 1 deletiondrivers/staging/pohmelfs/inode.c
- fs/9p/vfs_inode.c 0 additions, 1 deletionfs/9p/vfs_inode.c
- fs/affs/super.c 0 additions, 1 deletionfs/affs/super.c
- fs/afs/super.c 0 additions, 1 deletionfs/afs/super.c
- fs/befs/linuxvfs.c 0 additions, 1 deletionfs/befs/linuxvfs.c
- fs/bfs/inode.c 0 additions, 1 deletionfs/bfs/inode.c
- fs/block_dev.c 0 additions, 1 deletionfs/block_dev.c
- fs/btrfs/inode.c 0 additions, 1 deletionfs/btrfs/inode.c
- fs/ceph/inode.c 0 additions, 1 deletionfs/ceph/inode.c
- fs/coda/inode.c 0 additions, 1 deletionfs/coda/inode.c
- fs/ecryptfs/super.c 0 additions, 1 deletionfs/ecryptfs/super.c
- fs/efs/super.c 0 additions, 1 deletionfs/efs/super.c
- fs/exofs/super.c 0 additions, 1 deletionfs/exofs/super.c
- fs/ext2/super.c 0 additions, 1 deletionfs/ext2/super.c
- fs/ext3/super.c 0 additions, 1 deletionfs/ext3/super.c
- fs/ext4/super.c 0 additions, 1 deletionfs/ext4/super.c
- fs/fat/inode.c 0 additions, 1 deletionfs/fat/inode.c
- fs/freevxfs/vxfs_inode.c 0 additions, 1 deletionfs/freevxfs/vxfs_inode.c
- fs/fuse/inode.c 0 additions, 1 deletionfs/fuse/inode.c
Loading
Please register or sign in to comment