[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: Use pseudopath instead of fullpath in NFS v4 situations

2017-02-13 Thread GerritHub
>From Frank Filz : Frank Filz has uploaded a new change for review. ( https://review.gerrithub.io/348516 Change subject: Use pseudopath instead of fullpath in NFS v4 situations .. Use pseudopath

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: When logging exports, use the appropriate fullpath or pseudo...

2017-02-13 Thread GerritHub
>From Frank Filz : Frank Filz has uploaded a new change for review. ( https://review.gerrithub.io/348517 Change subject: When logging exports, use the appropriate fullpath or pseudopath .. When

Re: [Nfs-ganesha-devel] reg. FSAL_ACE_PERM_WRITE_DATA check in fsal_check_setattr_perms

2017-02-13 Thread Daniel Gryniewicz
Looking at the code, we don't check WRITE_DATA for owner checks, only for size or time changes. For owner/group changes, we check FSAL_ACE_PERM_WRITE_OWNER, which is the correct ACL to check. Presumably, you could just add an ACL to all files allowing all access to your "root" user. This

[Nfs-ganesha-devel] Change in ffilz/nfs-ganesha[next]: FSAL_PROXY (support_ex without state) : pxy_close2

2017-02-13 Thread GerritHub
>From Patrice LUCAS : Patrice LUCAS has uploaded a new change for review. ( https://review.gerrithub.io/348446 Change subject: FSAL_PROXY (support_ex without state) : pxy_close2 .. FSAL_PROXY (support_ex

[Nfs-ganesha-devel] reg. FSAL_ACE_PERM_WRITE_DATA check in fsal_check_setattr_perms

2017-02-13 Thread Satya Prakash GS
Hi, Ganesha seems to be checking for FSAL_ACE_PERM_WRITE_DATA permission to change owner/group perms (in the function fsal_check_setattr_perms). In our filesystem, there is another user who is equivalent to the root user. This user should be able to change owner/group of any file like the root

Re: [Nfs-ganesha-devel] reg. FSAL_ACE_PERM_WRITE_DATA check in fsal_check_setattr_perms

2017-02-13 Thread Frank Filz
> Looking at the code, we don't check WRITE_DATA for owner checks, only for > size or time changes. For owner/group changes, we check > FSAL_ACE_PERM_WRITE_OWNER, which is the correct ACL to check. > > Presumably, you could just add an ACL to all files allowing all access to your > "root" user.

Re: [Nfs-ganesha-devel] how does ganesha limit number of FDs

2017-02-13 Thread Frank Filz
Open fd tracking is an area Ganesha actually needs some additional work, however, the tracking in the non-support_ex methods did not limit the number of NFS v4 opens in any way, it just was used to manage how many fds Ganesha kept open for I/O access to files. With support_ex, an fd is