On Thu, Aug 16, 2012 at 08:47:03AM -0400, J. Bruce Fields wrote:
> > Hi Bruce, thinking a bit more I guess using general encode_fh is not that
> > convenient since it operates with dentries while our fdinfo output deals
> > with inodes. Thus I should either provide some new encode_fh variant
> > which would deal with inodes directly without "parents".
>
> I can't see why that wouldn't work.
>
> > Which doesn't
> > look for me anyhow better than the new export_encode_inode_fh helper.
>
> That isn't going to work for filesystems that define their own
> encode_fh:
>
> $ git grep '\.encode_fh'
> fs/btrfs/export.c: .encode_fh = btrfs_encode_fh,
> fs/ceph/export.c: .encode_fh = ceph_encode_fh,
...
Agreed. I'll try to cook something.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
