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)
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>

No differences found