-
- Downloads
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
- fs/proc/inode.c 0 additions, 1 deletionfs/proc/inode.c
- fs/qnx4/inode.c 0 additions, 1 deletionfs/qnx4/inode.c
- fs/reiserfs/super.c 0 additions, 1 deletionfs/reiserfs/super.c
- fs/romfs/super.c 0 additions, 1 deletionfs/romfs/super.c
- fs/squashfs/super.c 0 additions, 1 deletionfs/squashfs/super.c
- fs/sysv/inode.c 0 additions, 1 deletionfs/sysv/inode.c
- fs/ubifs/super.c 0 additions, 1 deletionfs/ubifs/super.c
- fs/udf/super.c 0 additions, 1 deletionfs/udf/super.c
- fs/ufs/super.c 0 additions, 1 deletionfs/ufs/super.c
- fs/xfs/xfs_iget.c 0 additions, 1 deletionfs/xfs/xfs_iget.c
- ipc/mqueue.c 0 additions, 1 deletionipc/mqueue.c
- mm/shmem.c 0 additions, 1 deletionmm/shmem.c
- net/sunrpc/rpc_pipe.c 0 additions, 1 deletionnet/sunrpc/rpc_pipe.c
Loading
Please register or sign in to comment