vfs: delete surplus inode NULL check
Each iteration of d_delete we reload inode from dentry->d_inode and then call S_ISDIR(inode-i_mode), so inode cannot possibly be NULL shortly afterwards unless something went horribly wrong. Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This commit is contained in:
parent
2903ff019b
commit
1fe0c0230a
|
@ -2109,7 +2109,7 @@ again:
|
||||||
inode = dentry->d_inode;
|
inode = dentry->d_inode;
|
||||||
isdir = S_ISDIR(inode->i_mode);
|
isdir = S_ISDIR(inode->i_mode);
|
||||||
if (dentry->d_count == 1) {
|
if (dentry->d_count == 1) {
|
||||||
if (inode && !spin_trylock(&inode->i_lock)) {
|
if (!spin_trylock(&inode->i_lock)) {
|
||||||
spin_unlock(&dentry->d_lock);
|
spin_unlock(&dentry->d_lock);
|
||||||
cpu_relax();
|
cpu_relax();
|
||||||
goto again;
|
goto again;
|
||||||
|
|
Loading…
Reference in New Issue