On Mon, Nov 04, 2019 at 10:36:03AM -0500, Chuck Lever wrote: > > Following the server's local file systems' mount options seems like a > good way to go. In particular, is there a need to expose user xattrs > on the server host, but prevent NFS clients' access to them? I can't > think of one. Ok, that sounds fine to me - I'll remove the user_xattr export flag, and we had already agreed to do away with the CONFIGs. That leaves one last item with regard to enabling support: the client side mount option. I assume the [no]user_xattr option should work the same as with other filesystems. What about the default setting? Also, currently, my code does not fail the mount operation if user xattrs are asked for, but the server does not support them. It just doesn't set NFS_CAP_XATTR for the server, and the xattr handler entry points eturn -EOPNOTSUPP, as they check for NFS_CAP_XATTR. What's the preferred behavior there? - Frank
