Bug 1035218

+++ This bug was initially created as a clone of Bug #1030443 +++

Description of problem:

While trying to run setfacl and getfacl command NFS ACLs behaviour is inconsistent
.
Version-Release number of selected component (if applicable):
glusterfs 3.4.0.43.1u2rhs

How reproducible:

create user acltest_user2
create file dot
Mount the gluster as NFS
mount -t nfs -o acl,vers=3 10.70.36.231:dist-rep2 /mnt/acl2/

[root@rhsauto010 acl2]# touch dot
[root@rhsauto010 acl2]# setfacl -m u:acltest_user2:rwx dot
[root@rhsauto010 acl2]# getfacl dot
getfacl: dot: Invalid argument
[root@rhsauto010 acl2]# setfacl -m u:acltest_user2:rwx dot
setfacl: dot: Invalid argument


Actual results:

getfacl and setfacl behaviour is inconsistent.

Expected results:

getfacl and setfacl command should execute successfully. 

Additional info:


[root@rhsauto001 ~]# gluster vol info
 
Volume Name: dist-rep2
Type: Distributed-Replicate
Volume ID: 65a2f89e-7d92-4632-b10e-bfc7119a8f9a
Status: Started
Number of Bricks: 6 x 2 = 12
Transport-type: tcp
Bricks:
Brick1: 10.70.36.236:/rhs/brick1/d2r12
Brick2: 10.70.36.237:/rhs/brick1/d2r22
Brick3: 10.70.36.236:/rhs/brick1/d4r12
Brick4: 10.70.36.237:/rhs/brick1/d4r22
Brick5: 10.70.36.236:/rhs/brick1/d6r12
Brick6: 10.70.36.237:/rhs/brick1/d6r22
Brick7: 10.70.36.231:/rhs/brick1/d1r12
Brick8: 10.70.36.233:/rhs/brick1/d1r22
Brick9: 10.70.36.231:/rhs/brick1/d3r12
Brick10: 10.70.36.233:/rhs/brick1/d3r22
Brick11: 10.70.36.231:/rhs/brick1/d5r12
Brick12: 10.70.36.233:/rhs/brick1/d5r22
Options Reconfigured:
nfs.export-dir: /test(localhost)
nfs.export-volumes: on
nfs.acl: on


[root@rhsauto001 ~]# rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100005    3   tcp  38465  mountd
    100005    1   tcp  38466  mountd
    100003    3   tcp   2049  nfs
    100024    1   udp  51728  status
    100024    1   tcp  52310  status
    100021    4   tcp  38468  nlockmgr
    100227    3   tcp   2049  nfs_acl
    100021    1   udp    735  nlockmgr
    100021    1   tcp    738  nlockmgr

--- Additional comment from RHEL Product and Program Management on 2013-11-14 08:08:35 EST ---

Since this issue was entered in bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

--- Additional comment from Anil Shah on 2013-11-15 01:58:21 EST ---

logs uploaded at location
rhsqe-repo.lab.eng.blr.redhat.com:/home/repo/sosreports/1030443

--- Additional comment from Raghavendra Talur on 2013-11-18 07:09:38 EST ---

Hi Anil,

Can you re-run the test after this command and see if it still fails?
Command: gluster volume set <VOLNAME> stat-prefetch off

--- Additional comment from Anil Shah on 2013-11-18 07:28:03 EST ---


No luck.

[root@rhsauto001 ~]# gluster volume set dist-rep2 stat-prefetch off
volume set: success


[root@rhsauto010 acl2]# touch dot
[root@rhsauto010 acl2]# getfacl dot
# file: dot
# owner: root
# group: root
user::rw-
group::r--
other::r--

[root@rhsauto010 acl2]# setfacl -m u:adm:rw dot 
[root@rhsauto010 acl2]# getfacl dot
# file: dot
# owner: root
# group: root
user::rw-
user:adm:rw-
group::r--
mask::rw-
other::r--

[root@rhsauto010 acl2]# setfacl -m u:adm:rw dot
[root@rhsauto010 acl2]# getfacl dot
getfacl: dot: Invalid argument
[root@rhsauto010 acl2]# rm -rf dot
[root@rhsauto010 acl2]# touch dot
[root@rhsauto010 acl2]# setfacl -m u:acltest_user2:rwx dot
[root@rhsauto010 acl2]# getfacl dot
getfacl: dot: Invalid argument

--- Additional comment from santosh pradhan on 2013-11-21 05:53:43 EST ---


The pcap shows that the permissions fetched by getfacl are garbage or wrong. 

It needs refactoring of acl3_getacl_cbk() code.