diff options
| author | Michel Lespinasse <walken@google.com> | 2012-03-26 17:32:44 -0700 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-04-02 09:27:19 -0700 |
| commit | 19f490da69bacce1d3b9934116bbff0ae5f50530 (patch) | |
| tree | 4e171896bf0298da5d17dacca9be76a0389dbaea /fs/dcache.c | |
| parent | 471320c7569290aeed04f9c730d92b67b9acb53d (diff) | |
| download | kernel_samsung_smdk4412-19f490da69bacce1d3b9934116bbff0ae5f50530.zip kernel_samsung_smdk4412-19f490da69bacce1d3b9934116bbff0ae5f50530.tar.gz kernel_samsung_smdk4412-19f490da69bacce1d3b9934116bbff0ae5f50530.tar.bz2 | |
vfs: fix d_ancestor() case in d_materialize_unique
commit b18dafc86bb879d2f38a1743985d7ceb283c2f4d upstream.
In d_materialise_unique() there are 3 subcases to the 'aliased dentry'
case; in two subcases the inode i_lock is properly released but this
does not occur in the -ELOOP subcase.
This seems to have been introduced by commit 1836750115f2 ("fix loop
checks in d_materialise_unique()").
Signed-off-by: Michel Lespinasse <walken@google.com>
[ Added a comment, and moved the unlock to where we generate the -ELOOP,
which seems to be more natural.
You probably can't actually trigger this without a buggy network file
server - d_materialize_unique() is for finding aliases on non-local
filesystems, and the d_ancestor() case is for a hardlinked directory
loop.
But we should be robust in the case of such buggy servers anyway. ]
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/dcache.c')
| -rw-r--r-- | fs/dcache.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/dcache.c b/fs/dcache.c index f598b98..0b51cfc 100644 --- a/fs/dcache.c +++ b/fs/dcache.c @@ -2433,6 +2433,7 @@ struct dentry *d_materialise_unique(struct dentry *dentry, struct inode *inode) if (d_ancestor(alias, dentry)) { /* Check for loops */ actual = ERR_PTR(-ELOOP); + spin_unlock(&inode->i_lock); } else if (IS_ROOT(alias)) { /* Is this an anonymous mountpoint that we * could splice into our tree? */ @@ -2442,7 +2443,7 @@ struct dentry *d_materialise_unique(struct dentry *dentry, struct inode *inode) goto found; } else { /* Nope, but we must(!) avoid directory - * aliasing */ + * aliasing. This drops inode->i_lock */ actual = __d_unalias(inode, dentry, alias); } write_sequnlock(&rename_lock); |