From: Neil Brown <neilb@suse.de>
To: Steven French <sfrench@us.ibm.com>
Cc: akpm@linux-foundation.org, hch@infradead.org,
Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree
Date: Thu, 17 May 2007 14:26:56 +1000 [thread overview]
Message-ID: <17995.55696.89329.396629@notabene.brown> (raw)
In-Reply-To: message from Steven French on Wednesday May 16
>On Wednesday May 16, sfrench@us.ibm.com wrote:
> > If CIFS provides some fix-length identifier for files, then
> > you might be able to do it
>
> Most CIFS servers (Windows on NTFS, Samba etc.) can return a "unique
> identifier" (a 64 bit inode number), in conjunction with the volume id,
> that is probably good enough ... right? This can be returned on various
> calls (level 0x03EE "file_internal_info" - returns only this number). If
> reverse lookup is required - ie given a "unique identifier" what is its
> path name - there are probably a few different ways to handle this but
> presumably local filesystems run into the same issue.
Yes, that "unique identifier" sounds like it would be suitable to put
in the filehandle.
But reverse lookup is definitely required.
Providing you can turn this into a 'struct inode *' in the filesystem,
the code in exportfs/ can help turn that into a fully connected
dentry.
NeilBrown
next prev parent reply other threads:[~2007-05-17 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705152152.l4FLqJsV018874@shell0.pdx.osdl.net>
2007-05-16 6:57 ` + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree Christoph Hellwig
2007-05-16 12:53 ` Christoph Hellwig
2007-05-16 14:55 ` Steven French
2007-05-16 16:02 ` J. Bruce Fields
2007-05-16 17:03 ` Steven French
2007-05-16 21:33 ` J. Bruce Fields
2007-05-17 0:05 ` Neil Brown
2007-05-17 3:11 ` Steven French
2007-05-17 4:26 ` Neil Brown [this message]
2007-05-22 9:10 ` Christoph Hellwig
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=17995.55696.89329.396629@notabene.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sfrench@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).