On Tue, May 02, 2000 at 01:50:16PM -0700, Chris Mason wrote:
>
> ReiserFS has unique inode numbers, but they aren't enough to actually find
> the inode on disk. That requires the inode number, and another 32 bits of
> information we call the packing locality. The packing locality starts as
> the parent directory inode number, but does not change across renames.
>
> So, we need to add a fh_to_dentry lookup operation for knfsd to use, and
> perhaps a dentry_to_fh operation as well (but _fh_update in pre6 looks ok
> for us).
First off, could we call them "inode labels" or something less confusing?
"file" outside of NFS has a different meaning (semantic namespace collision
<g>) Also, I don't see how a "fh_to_dentry" (or ilbl_to_dentry) is going to
work - (think hardlinks, etc.). You do need an iget_by_label or something
similar though. Details that need to be worked out would be max label size
and how they're passed around (void * ptr and a length?)
Also, what are the size constraints imposed by NFS? What about other network
filesystems?
