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>

1 files changed, 1 insertions, 1 deletions

diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c
index da52cdbe8388..ffa2be57804d 100644
--- a/fs/ecryptfs/inode.c
+++ b/fs/ecryptfs/inode.c
@@ -269,8 +269,8 @@ ecryptfs_create(struct inode *directory_inode, struct dentry *ecryptfs_dentry,
                 iput(ecryptfs_inode);
                 goto out;
         }
-        d_instantiate(ecryptfs_dentry, ecryptfs_inode);
         unlock_new_inode(ecryptfs_inode);
+        d_instantiate(ecryptfs_dentry, ecryptfs_inode);
 out:
         return rc;
 }