From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: aneesh.kumar@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: encode_fh: have inode but no dentry
Date: Thu, 24 Feb 2011 13:16:34 -0800 (PST) [thread overview]
Message-ID: <c4d12fe2-2175-4d59-9ef2-e6d5996023f0@default> (raw)
Hi Aneesh --
I see you are continuing with encode_fh related
development so I thought I would bring this up
with you.
I have a need to call the encode_fh op in a
situation where I have an inode but not a dentry,
and calling d_find_alias(inode) sometimes returns
NULL. In my usage, connectable is always zero, so
having just the inode should be sufficient to get
useful results from encode_fh, at least for the
filesystems I've looked at.
What I'd like to see is the generic interface to
encode_fh extended to support this situation,
probably by passing inode as another parameter,
perhaps specified so that it can only be non-NULL
if connectable==0 and dentry==NULL.
Such a change would require a patch that touched
nearly every filesystem so it's clearly not to
be taken lightly.
Any thoughts on this?
Thanks,
Dan
next reply other threads:[~2011-02-24 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 21:16 Dan Magenheimer [this message]
2011-02-24 21:23 ` encode_fh: have inode but no dentry Al Viro
2011-02-24 21:51 ` Dan Magenheimer
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=c4d12fe2-2175-4d59-9ef2-e6d5996023f0@default \
--to=dan.magenheimer@oracle.com \
--cc=aneesh.kumar@linux.vnet.ibm.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