ufs: Fix warning from unlock_new_inode()
authorJan Kara <jack@suse.cz>
Mon, 1 Jun 2015 12:52:04 +0000 (14:52 +0200)
committerAl Viro <viro@zeniv.linux.org.uk>
Tue, 16 Jun 2015 06:08:07 +0000 (02:08 -0400)
Commit e4502c63f56aeca88 (ufs: deal with nfsd/iget races) introduced
unlock_new_inode() call into ufs_add_nondir(). However that function
gets called also from ufs_link() which hands it already initialized
inode and thus unlock_new_inode() complains. The problem is harmless but
annoying.

Fix the problem by opencoding necessary stuff in ufs_link()

Fixes: e4502c63f56aeca887ced37f24e0def1ef11cec8
Signed-off-by: Jan Kara <jack@suse.cz>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fs/ufs/namei.c

index 1f5223c9e1e2c94ac22f94de629da756fbce8e8c..2346b83fa12baee5a6bc5f2fe572d382c051a74a 100644 (file)
@@ -174,7 +174,12 @@ static int ufs_link (struct dentry * old_dentry, struct inode * dir,
        inode_inc_link_count(inode);
        ihold(inode);
 
-       error = ufs_add_nondir(dentry, inode);
+       error = ufs_add_link(dentry, inode);
+       if (error) {
+               inode_dec_link_count(inode);
+               iput(inode);
+       } else
+               d_instantiate(dentry, inode);
        unlock_ufs(dir->i_sb);
        return error;
 }