Files
android_kernel_xiaomi_sm8450/fs/nfs
Su Yanjun fe1e8dbec1 NFSv3: FIx bug when using chacl and chmod to change acl
We find a bug when running test under nfsv3  as below.
1)
chacl u::r--,g::rwx,o:rw- file1
2)
chmod u+w file1
3)
chacl -l file1

We expect u::rw-, but it shows u::r--, more likely it returns the
cached acl in inode.

We dig the code find that the code path is different.

chacl->..->__nfs3_proc_setacls->nfs_zap_acl_cache
Then nfs_zap_acl_cache clears the NFS_INO_INVALID_ACL in
NFS_I(inode)->cache_validity.

chmod->..->nfs3_proc_setattr
Because NFS_INO_INVALID_ACL has been cleared by chacl path,
nfs_zap_acl_cache wont be called.

nfs_setattr_update_inode will set NFS_INO_INVALID_ACL so let it
before nfs_zap_acl_cache call.

Signed-off-by: Su Yanjun <suyanjun218@gmail.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
2020-01-15 10:54:33 -05:00
..
2020-01-15 10:54:33 -05:00
2020-01-15 10:54:33 -05:00
2020-01-15 10:54:30 -05:00
2019-02-20 15:14:21 -05:00
2020-01-15 10:54:31 -05:00
2020-01-15 10:15:17 -05:00
2020-01-15 10:15:17 -05:00
2015-04-23 15:16:14 -04:00
2020-01-15 10:54:31 -05:00
2019-10-09 12:05:49 -04:00
2020-01-15 10:54:33 -05:00
2020-01-15 10:54:33 -05:00