From: linux@horizon.com
To: brianhsu.hsu@qmail.com, linux-kernel@vger.kernel.org
Subject: Re: How to get dentry from inode number?
Date: 29 Jul 2005 11:28:49 -0400 [thread overview]
Message-ID: <20050729152849.29241.qmail@science.horizon.com> (raw)
> How can I get a full pathname from an inode number ? (Our data
> structure only keep track inode number instead of pathname in
> order to keep thin, so don't have any information but inode
> number.)
Except in extreme circumstances (there's some horrible kludgery in the
NFS code), you don't. Just store a dentry pointer to begin with; it's
easy to map from dentry to inode.
In addition to files with multiple names, you can have files with no
names, made by the usual Unix trick of deleting a file after opening it.
The NFS kludgery is required by the short-sighted design of the NFS
protocol. Don't emulate it, or you will be lynched by a mob of angry
kernel developers with torches and pitchforks.
next reply other threads:[~2005-07-29 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 15:28 linux [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-29 15:02 墳墓
2005-07-29 15:11 ` Jörn Engel
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=20050729152849.29241.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=brianhsu.hsu@qmail.com \
--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®