>On Wednesday May 16, sfrench@xxxxxxxxxx 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 - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
