diff options
| author | Sage Weil <sage@newdream.net> | 2011-05-24 13:06:05 -0700 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2011-05-26 07:26:46 -0400 |
| commit | 64252c75a2196a0cf1e0d3777143ecfe0e3ae650 (patch) | |
| tree | 8534f12a507ef5aee91e302f3e54cf8a4440fc82 /fs/namei.c | |
| parent | 48293699a09324d2e3c66bd53d10eed6d67937a0 (diff) | |
| download | kernel_samsung_smdk4412-64252c75a2196a0cf1e0d3777143ecfe0e3ae650.zip kernel_samsung_smdk4412-64252c75a2196a0cf1e0d3777143ecfe0e3ae650.tar.gz kernel_samsung_smdk4412-64252c75a2196a0cf1e0d3777143ecfe0e3ae650.tar.bz2 | |
vfs: remove dget() from dentry_unhash()
This serves no useful purpose that I can discern. All callers (rename,
rmdir) hold their own reference to the dentry.
A quick audit of all file systems showed no relevant checks on the value
of d_count in vfs_rmdir/vfs_rename_dir paths.
Signed-off-by: Sage Weil <sage@newdream.net>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/namei.c')
| -rw-r--r-- | fs/namei.c | 5 |
1 files changed, 1 insertions, 4 deletions
@@ -2545,10 +2545,9 @@ SYSCALL_DEFINE2(mkdir, const char __user *, pathname, int, mode) */ void dentry_unhash(struct dentry *dentry) { - dget(dentry); shrink_dcache_parent(dentry); spin_lock(&dentry->d_lock); - if (dentry->d_count == 2) + if (dentry->d_count == 1) __d_drop(dentry); spin_unlock(&dentry->d_lock); } @@ -2575,7 +2574,6 @@ int vfs_rmdir(struct inode *dir, struct dentry *dentry) dentry->d_inode->i_flags |= S_DEAD; dont_mount(dentry); } - dput(dentry); } } mutex_unlock(&dentry->d_inode->i_mutex); @@ -3002,7 +3000,6 @@ static int vfs_rename_dir(struct inode *old_dir, struct dentry *old_dentry, mutex_unlock(&target->i_mutex); if (d_unhashed(new_dentry)) d_rehash(new_dentry); - dput(new_dentry); } if (!error) if (!(old_dir->i_sb->s_type->fs_flags & FS_RENAME_DOES_D_MOVE)) |