From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-nfs-owner@vger.kernel.org Received: from fieldses.org ([174.143.236.118]:49115 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753502Ab3IFPny (ORCPT ); Fri, 6 Sep 2013 11:43:54 -0400 From: "J. Bruce Fields" To: Al Viro Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, "J. Bruce Fields" Subject: [PATCH 3/3] dcache: don't clear DCACHE_DISCONNECTED too early Date: Fri, 6 Sep 2013 11:43:50 -0400 Message-Id: <1378482230-16312-3-git-send-email-bfields@redhat.com> In-Reply-To: <1378482230-16312-1-git-send-email-bfields@redhat.com> References: <1378482230-16312-1-git-send-email-bfields@redhat.com> Sender: linux-nfs-owner@vger.kernel.org List-ID: From: "J. Bruce Fields" 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. Signed-off-by: J. Bruce Fields --- fs/dcache.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/dcache.c b/fs/dcache.c index ec66780..69f1ba0 100644 --- a/fs/dcache.c +++ b/fs/dcache.c @@ -2396,7 +2396,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; } /** -- 1.7.9.5