On Fri, Nov 11, 2016 at 11:04 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > So if I'm reading right, the setup is > > nfs client---NFSv3--->knfsd---FUSE-->gluster > > I hate to just pass the buck, but my bet is on the issue being either on > the gluster side, or on limitations of the fuse protocol itself. > > Cc'ing Miklos as I believe he did the original fuse nfsd export > implementation. Miklos, does fuse has a way for file owners to override > permissions? We need this sometimes because for example, an application > may hold a write open on a read-only file, but the server doesn't itself > already have an open (which can happen for lots of reasons). Is glusterfs using "default_permissions" fuse option? If so, then the above shouldn't be an issue, since permission checking is done by generic_permission() which works the same for all filesystems. If not, then there's the same problem as re-exporting NFSv4 as NFSv3 would have: the permissions are not checked in ->permission(), but in e.g. ->atomic_open() so nfsd's override mechanism wouldn't work. Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
