From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dcache: trivial comment fix
Date: Mon, 10 Sep 2007 14:54:00 -0400 [thread overview]
Message-ID: <20070910185400.GG2947@fieldses.org> (raw)
In-Reply-To: <20070910184632.GF2947@fieldses.org>
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?
--b.
next prev parent reply other threads:[~2007-09-10 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 18:46 [PATCH] dcache: trivial comment fix J. Bruce Fields
2007-09-10 18:54 ` J. Bruce Fields [this message]
2007-09-11 17:33 ` Neil Brown
2007-09-11 18:00 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
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=20070910185400.GG2947@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@linux-foundation.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