From: Sunil Mushran <sunil.mushran@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Track negative dentries
Date: Mon, 21 Jun 2010 10:08:04 -0700 [thread overview]
Message-ID: <4C1F9C74.1060403@oracle.com> (raw)
In-Reply-To: <20100621042716.GA2735@laptop.us.oracle.com>
On 06/20/2010 09:27 PM, Wengang Wang wrote:
> Hi Goldwyn,
>
> Has you ever test the hit race?
> Actually I also wrote the codes locally monthes ago. When I was testing it,
> I found the dentry are different memory objects. For example, fileA is not
> exist, we issue a command of 'ls -l /path/to/fileA', At the first run, set
> parent ino to dentry. At the second run, the parent ino is not there. By
> printing the address, I found the two dentries are different ones though
> they are both for "fileA".
> So I wonder if you tested it.
>
>
I am trying to understand your issue.
Do you mean you encountered a case in which there were two
dentries for the same directory entry (/path/to/fileA) but one had
a correct parent inode and the other had no parent inode.
Note that a dentry points to a parent dentry that points to the inode.
So are you claiming that the two dentries pointed to two different parent
dentries one of which had the correct inode the other null inode?
Sunil
next prev parent reply other threads:[~2010-06-21 17:08 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 [this message]
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
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=4C1F9C74.1060403@oracle.com \
--to=sunil.mushran@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).