Re: [Nfs-ganesha-devel] unlink bypasses access checks

2017-05-10 Thread Frank Filz
> Certain checks are delegated to the FSALs, for performance reasons. The > access check on unlink is one of these (see fsal_remove()). If you build with > ENABLE_RFC_ACL, it will perform those checks in the common code, but this > will result in more getattrs() calls into the FSAL, which raise

Re: [Nfs-ganesha-devel] unlink bypasses access checks

2017-05-10 Thread Daniel Gryniewicz
Certain checks are delegated to the FSALs, for performance reasons. The access check on unlink is one of these (see fsal_remove()). If you build with ENABLE_RFC_ACL, it will perform those checks in the common code, but this will result in more getattrs() calls into the FSAL, which raises late

[Nfs-ganesha-devel] unlink bypasses access checks

2017-05-09 Thread Naresh Babu
Like all other NFS ops, unlink/remove is preceded by an access call. nfs3_access on parent directory (under which file is being removed) returns a response with res->res_access3.ACCESS3res_u.resok.access set to permissions allowed on the parent directory. Since the current user doesn't have write p