Hi,
POSIX ACL and Richacl want to apply umask on file creation only when we don't have any
inheritable ACEs on the parent directory. Currently with nfsv4 code we do
check for POSIX ACL in nfs_atomic_lookup, but i don't find where we set
the MS_POSIXACL bit for the nfsv4 code.
Even if we try to do something like below
if (nfs4_server_supports_acls(..))
sb->s_flags |= MS_POSIXACL;
I guess we could get it wrong. The above implies we may end up not
applying umask for a server supporting ACL even if the parent
directory don't have inheritable ACEs.
I found a proposal to add umask attribute at
http://www.ietf.org/mail-archive/web/nfsv4/current/msg07159.html
http://www.ietf.org/proceedings/74/slides/nfsv4-3.pdf
So what is the expected behaviour for NFS. Should we always apply
umask (which is what it currently does) irrespective of whether
parent directory have inheritable ACEs or not ?
-aneesh
--
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
