From: Wengang Wang <wen.gang.wang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Track negative dentries
Date: Wed, 23 Jun 2010 12:57:24 +0800 [thread overview]
Message-ID: <20100623045724.GA2426@laptop.us.oracle.com> (raw)
In-Reply-To: <20100622165342.GH28091@wotan.suse.de>
Thanks Mark!
The patch works fine.
I went to a wrong direction.
regards,
wengang.
On 10-06-22 09:53, Mark Fasheh wrote:
> On Tue, Jun 22, 2010 at 11:23:33AM +0800, Wengang Wang wrote:
> > Actually I meant two dentries in the two run of 'ls -l'.
> > At the first run, a dentry, dentry A, is created. Because fileA doesn't exist,
> > dentry->d_inode is NULL.
>
> Ok so you do a lookup on a name which doesn't exist, which results in a
> negative dentry for fileA.
>
> > Then a do_revalidate() is run, ocfs2_dentry_revalidate() returns "not
> > valid" since d_inode is NULL. Thus the dentry A is unhashed from cache by
> > d_invalidate().
>
> Part of the patch is to change this behavior right here.
>
> ocfs2_dentry_revalidate() is seeing the NULL inode and forcing the dentry to
> be invalidated (thus requiring another lookup).
>
>
> The patch needs to handle this by comparing sequence numbers with the parent
> dentry and ONLY if they're different should it force the dentry to be
> invalidated. Otherwise it can allow the dentry to stay hashed (and
> negative).
> --Mark
>
> --
> Mark Fasheh
next prev parent reply other threads:[~2010-06-23 4:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-18 15:02 [Ocfs2-devel] [PATCH] Track negative dentries Goldwyn Rodrigues
2010-06-18 16:06 ` Sunil Mushran
2010-06-23 18:25 ` Goldwyn Rodrigues
2010-06-23 19:05 ` Sunil Mushran
2010-06-23 20:27 ` Goldwyn Rodrigues
2010-06-23 21:01 ` Joel Becker
2010-06-23 21:32 ` Goldwyn Rodrigues
2010-06-21 4:27 ` Wengang Wang
2010-06-21 17:08 ` Sunil Mushran
2010-06-22 3:23 ` Wengang Wang
2010-06-22 3:36 ` Joel Becker
2010-06-22 5:22 ` Wengang Wang
2010-06-22 5:38 ` Sunil Mushran
2010-06-22 6:14 ` Wengang Wang
2010-06-22 16:53 ` Mark Fasheh
2010-06-23 4:57 ` Wengang Wang [this message]
2010-06-23 18:30 ` Goldwyn Rodrigues
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100623045724.GA2426@laptop.us.oracle.com \
--to=wen.gang.wang@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).