From: Christopher Li <chrisl@vmware.com>
To: "'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 17:26:13 -0800 [thread overview]
Message-ID: <20021106172613.C7475@vmware.com> (raw)
In-Reply-To: <20021106094425.GP588@clusterfs.com>; from adilger@clusterfs.com on Wed, Nov 06, 2002 at 02:44:25AM -0700
On Wed, Nov 06, 2002 at 02:44:25AM -0700, Andreas Dilger wrote:
> 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.
Thanks for the explain. Then there is no problem then.
Chris
prev parent reply other threads:[~2002-11-06 22:20 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
2002-11-07 1:26 ` Christopher Li [this message]
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=20021106172613.C7475@vmware.com \
--to=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 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.