From: Neil Brown <neilb@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dcache: trivial comment fix
Date: Tue, 11 Sep 2007 19:33:43 +0200 [thread overview]
Message-ID: <18150.53623.525080.865402@notabene.brown> (raw)
In-Reply-To: message from J. Bruce Fields on Monday September 10
On Monday September 10, bfields@fieldses.org wrote:
> On Mon, Sep 10, 2007 at 02:46:32PM -0400, J. Bruce Fields wrote:
> > * This forceful removal will result in ugly /proc output if
> > * somebody holds a file open that got deleted due to a rename.
> > * We could be nicer about the deleted file, and let it show
> > - * up under the name it got deleted rather than the name that
> > - * deleted it.
> > + * up under the name it had before it was deleted rather than
> > + * under the original name of the file that was moved on top of it.
>
> By the way, on further examination of the code it doesn't actually do
> what's described in the case where the target name is large and the
> moved-from name is small. Instead, it reports random garbage (usually
> part of a name left over from some other dentry?) as far as I can tell:
>
> from switch_names():
>
>
> if (dname_external(target)) {
> if (dname_external(dentry)) {
> ...
> } else {
> /*
> * dentry:internal, target:external. Steal target's
> * storage and make target internal.
> */
> dentry->d_name.name = target->d_name.name;
> target->d_name.name = target->d_iname;
>
> ... but target->d_iname could have anything in it, right?
Right, but not relevant.
The name "switch_names" is somewhat misleading. It is really
"copyname" or similar. From the comment at the top:
* When switching names, the actual string doesn't strictly have to
* be preserved in the target - because we're dropping the target
* anyway. As such, we can just do a simple memcpy() to copy over
* the new name before we switch.
so the apparent name of 'target' after the 'swap' is not important.
The purpose of the assignment
target->d_name.name = target->d_iname;
is to make "dname_external(target)" false, that making "target
internal" as the comment says.
static inline int dname_external(struct dentry *dentry)
{
return dentry->d_name.name != dentry->d_iname;
}
This could possibly be made a little more clear....
NeilBrown
next prev parent reply other threads:[~2007-09-11 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 18:46 J. Bruce Fields
2007-09-10 18:54 ` J. Bruce Fields
2007-09-11 17:33 ` Neil Brown [this message]
2007-09-11 18:00 ` J. Bruce Fields
2007-10-16 19:32 J. Bruce Fields
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=18150.53623.525080.865402@notabene.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.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
all inboxes | Powered by JetHome®