From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
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 13:51:03 -0800 (PST) [thread overview]
Message-ID: <b787274a-de5f-4a0d-957e-d5a9c2f2d752@default> (raw)
In-Reply-To: <20110224212317.GD22723@ZenIV.linux.org.uk>
> From: Al Viro [mailto:viro@ZenIV.linux.org.uk]
> Subject: Re: encode_fh: have inode but no dentry
>
> 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?
(Wow, that was fast! /me pictures a 64-core Al Viro
parallelizing incoming lkml email.)
It's for some work I'm building on top of cleancache.
Since cleancache isn't merged (yet), it's not pressing,
but this seemed a reasonable approach so, before I
started looking at more complicated alternatives,
I thought I'd get some idea if this is feasible or not.
The situation arises when the inode is in cache but
the dentry is not, but I still need a filehandle.
In the non-connectable case, this should still be OK.
Seems like a case that might be more broadly useful.
Thanks,
Dan
prev parent reply other threads:[~2011-02-24 21:53 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
2011-02-24 21:51 ` Dan Magenheimer [this message]
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=b787274a-de5f-4a0d-957e-d5a9c2f2d752@default \
--to=dan.magenheimer@oracle.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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