From: Andreas Dilger <adilger@clusterfs.com>
To: Christopher Li <chrisl@vmware.com>
Cc: "'Jeremy Fitzhardinge '" <jeremy@goop.org>,
"'Ext2 devel '" <ext2-devel@lists.sourceforge.net>,
"'Linux Kernel List '" <linux-kernel@vger.kernel.org>
Subject: Re: [Ext2-devel] bug in ext3 htree rename: doesn't delete old nam e, leaves ino with bad nlink
Date: Wed, 6 Nov 2002 02:44:25 -0700 [thread overview]
Message-ID: <20021106094425.GP588@clusterfs.com> (raw)
In-Reply-To: <3C77B405ABE6D611A93A00065B3FFBBA080B3D@PA-EXCH2>
On Nov 06, 2002 01:03 -0800, Christopher Li wrote:
> Jeremy Fitzhardinge wrote:
> >Update it in what way? In principle a rename is an atomic operation, so
> >other things shouldn't be able to observe the directory in an
> >intermediate state.
>
> I mean when split dir entry blocks, it will move the dir entry inside
> that block. I am not clear about do we need to invalidate the dentry
> cache for those changed entry. I need to check the source.
I am not aware of anything stored in a dentry which would be affected
by the directory or changes therein at all. The file name is allocated
as part of the dentry, and also only holds an inode pointer.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-11-06 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 9:03 [Ext2-devel] bug in ext3 htree rename: doesn't delete old nam e, leaves ino with bad nlink Christopher Li
2002-11-06 9:44 ` Andreas Dilger [this message]
2002-11-07 1:26 ` Christopher Li
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=20021106094425.GP588@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=chrisl@vmware.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
/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