From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: aneesh.kumar@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: encode_fh: have inode but no dentry
Date: Thu, 24 Feb 2011 21:23:17 +0000 [thread overview]
Message-ID: <20110224212317.GD22723@ZenIV.linux.org.uk> (raw)
In-Reply-To: <c4d12fe2-2175-4d59-9ef2-e6d5996023f0@default>
On Thu, Feb 24, 2011 at 01:16:34PM -0800, Dan Magenheimer wrote:
> 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.
[snip]
> 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?
How about "tell us what do you need that for", for starters?
next prev parent reply other threads:[~2011-02-24 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 21:16 encode_fh: have inode but no dentry Dan Magenheimer
2011-02-24 21:23 ` Al Viro [this message]
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=20110224212317.GD22723@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dan.magenheimer@oracle.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