don't expose I_NEW inodes via dentry->d_inode
authorAl Viro <viro@zeniv.linux.org.uk>
Thu, 19 Jul 2012 05:18:15 +0000 (09:18 +0400)
committerAl Viro <viro@zeniv.linux.org.uk>
Sun, 22 Jul 2012 20:00:58 +0000 (00:00 +0400)
commit8fc37ec54cd8e37193b0d42809b785ff19661c34
tree12040128b054dc1b163433358b0fd2b8ec843762
parent32a7991b6a9c758e4e2b8166c5e1cc7563c3dcde
don't expose I_NEW inodes via dentry->d_inode

d_instantiate(dentry, inode);
unlock_new_inode(inode);

is a bad idea; do it the other way round...

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fs/ecryptfs/inode.c
fs/ext2/namei.c
fs/ext3/namei.c
fs/ext4/namei.c
fs/jffs2/dir.c
fs/jfs/namei.c
fs/reiserfs/namei.c