Description of problem: The caching of GF_POSIX_ACL_DEFAULT and GF_POSIX_ACL_ACCESS keys is not done correctly because mdc_key_load_set() tries to enable the caching with an inappropriate prefix. "glusterfs.posix_acl." does not match "glusterfs.posix.acl" nor "glusterfs.posix.default_acl" Version-Release number of selected component (if applicable): 3.8
REVIEW: https://review.gluster.org/17909 (md-cache: Use correct xattr keynames for virtual glusterfs ACLs.) posted (#1) for review on master by Günther Deschner (gd)
COMMIT: https://review.gluster.org/17909 committed in master by Jeff Darcy (jeff.us) ------ commit 5fe8555800cbc9818e7c976f63499795a378cd8d Author: Günther Deschner <gd> Date: Wed Jul 26 18:10:33 2017 +0200 md-cache: Use correct xattr keynames for virtual glusterfs ACLs. The "glusterfs.posix_acl." prefix does not catch the glusterfs posix acl xattr keynames which are * "glusterfs.posix.acl" and * "glusterfs.posix.default_acl" Using the GF_POSIX_ACL_ACCESS and GF_POSIX_ACL_DEFAULT defines directly is the savest option. Guenther Change-Id: I5aba64b26b6cbec850ea02316dd9f069400e857f BUG: 1476295 Signed-off-by: Guenther Deschner <gd> Reviewed-on: https://review.gluster.org/17909 Reviewed-by: Michael Adam <obnox> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos> Tested-by: Niels de Vos <ndevos> CentOS-regression: Gluster Build System <jenkins.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/