diff options
| author | J. Bruce Fields | 2012-07-18 16:27:37 -0600 |
|---|---|---|
| committer | Al Viro | 2013-11-09 00:16:34 -0500 |
| commit | f80de2cde10350b8d146e375ff8b634e72e6a827 (patch) | |
| tree | ccf04843c4f83de44836f6cf265c6e761358b420 /fs | |
| parent | e1a24bb0aa6abaa86b5a95638722ea2036dbaadd (diff) | |
dcache: don't clear DCACHE_DISCONNECTED too early
DCACHE_DISCONNECTED should not be cleared until we're sure the dentry is
connected all the way up to the root of the filesystem. It *shouldn't*
be cleared as soon as the dentry is connected to a parent. That will
cause bugs at least on exportable filesystems.
Acked-by: Christoph Hellwig <hch@infradead.org>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs')
| -rw-r--r-- | fs/dcache.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/fs/dcache.c b/fs/dcache.c index 67662beebc72..72c99b88d264 100644 --- a/fs/dcache.c +++ b/fs/dcache.c @@ -2757,7 +2757,6 @@ static void __d_materialise_dentry(struct dentry *dentry, struct dentry *anon) spin_unlock(&dentry->d_lock); /* anon->d_lock still locked, returns locked */ - anon->d_flags &= ~DCACHE_DISCONNECTED; } /** |