On Wed, Nov 14, 2012 at 08:26:22AM -0500, J. Bruce Fields wrote: > On Wed, Nov 14, 2012 at 05:03:47PM +0400, Cyrill Gorcunov wrote: > > On Wed, Nov 14, 2012 at 07:45:49AM -0500, J. Bruce Fields wrote: > > > > > > > > We can try going this route, what do you think? > > > > > > I still don't understand why you need a dentry to get the filehandle. > > > The current api may ask for one, but it shouldn't really be necessary > > > (assuming you don't want parent directory information encoded in the > > > filehandle, which I hope you don't). > > > > As far as I know we don't need parent encoded. So Bruce, you think > > to modify exportfs instead to work with inode directly? > > Looks like the filesystem encode_fh method just takes inodes (with the > parent inode allowed to be NULL), so all you'd need would be a version > of exportfs_encode_fh that took an inode. > > (Worst case, if that didn't work, you could fake up a dentry with > something like d_obtain_alias, but better not to if it's not necessary.) Yeah, I'll update the series, test it and show ther results. Thanks! Cyrill -- 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
