+++ This bug was initially created as a clone of Bug #1277877 +++ Description of problem: If only one DENY entry is set for the user/group ,then all of the existing permission(by default it will permission of everyone) will be lost Version-Release number of selected component (if applicable): mainline How reproducible: always Steps to Reproduce: 1.Export a gluster volume via ganesha with acls enabled 2.Mount the volume using nfsv4 3.create a file 4.Now set a DENY ENTRY for that file(no corresponding ALLOW ENTRY should exist) example at the mount point # touch file # nfs4_getfacl file A::OWNER@:rwatTcCy A::GROUP@:rtcy A::EVERYONE@:rtcy nfs4_setfacl -a D::user_b@{$DOMAIN}:W file Actual results: nfs4_getfacl file A::OWNER@:rwatTcCy D::user_b@{$DOMAIN}:rwa A::user_b@{$DOMAIN}:tcy A::GROUP@:rtcy A::EVERYONE@:rtcy Expected results: nfs4_getfacl file A::OWNER@:rwatTcCy D::user_b@{$DOMAIN}:wa A::user_b@{$DOMAIN}:rtcy A::GROUP@:rtcy A::EVERYONE@:rtcy Additional info:
The patch is sent for upstream for review https://review.gerrithub.io/#/c/251342/
tested it on latest build, i.e. nfs-ganesha-2.2.0-11.el7rhgs.x86_64 and result is as expected, # nfs4_getfacl /mnt/acl-test/fil1 A::OWNER@:rwatTcCy D::ric.blr.redhat.com:wa A::ric.blr.redhat.com:rtcy A::GROUP@:rwatcy A::EVERYONE@:rwatcy
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html