From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] Ocfs2: Stop tracking a negative dentry after dentry_iput().
Date: Thu, 18 Nov 2010 15:38:33 -0800 [thread overview]
Message-ID: <20101118233833.GG19821@mail.oracle.com> (raw)
In-Reply-To: <4CE48A84.3090405@oracle.com>
On Thu, Nov 18, 2010 at 10:08:04AM +0800, Tristan Ye wrote:
> Tristan Ye wrote:
> >> I'm going to take this fix for now, because it is clearing the
> >> problem. However, it looks like the original code _should_ work. If we
> >> have created a file, the directory's generation should have been
> >> updated. Thus, the pgen shouldn't match the generation set when the old
> >> inode was deleted. Right?
> I'm afraid it was not the case,
>
> Say nodeA deleted the file(after Node B 'ls' it), Yes, now the
> generation number of
> parent directory gets updated, and the newly-generated negative dentry
> inherits the
> pgen, then we continue to do the creation(touch file) on nodeA without
> nodeB interleaves
> the operation at all. in this case, pgen will not change since no
> dlmlock gets converted here,
> reasonable?
Makes sense. And since we're trying to avoid the cluster lock
with our validation, we can't take it to check. Thanks.
Joel
--
"Anything that is too stupid to be spoken is sung."
- Voltaire
Joel Becker
Senior Development Manager
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-11-18 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 13:39 [Ocfs2-devel] [PATCH 1/1] Ocfs2: Stop tracking a negative dentry after dentry_iput() Tristan Ye
2010-11-17 23:23 ` Joel Becker
2010-11-18 1:42 ` Tristan Ye
2010-11-18 2:08 ` Tristan Ye
2010-11-18 23:38 ` Joel Becker [this message]
2010-11-18 23:43 ` Joel Becker
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=20101118233833.GG19821@mail.oracle.com \
--to=joel.becker@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.