REVIEW: http://review.gluster.org/12939 (storage/posix: fix dict leak in posix_fgetxattr) posted (#1) for review on release-3.7 by Susant Palai (spalai)
REVIEW: http://review.gluster.org/13040 (afr: refresh inode using fstat) posted (#1) for review on release-3.7 by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/13040 (afr: refresh inode using fstat) posted (#2) for review on release-3.7 by Ravishankar N (ravishankar)
COMMIT: http://review.gluster.org/13040 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit f88369e75fc2482eec68da798d849acaa30c5de8 Author: Ravishankar N <ravishankar> Date: Mon Dec 7 18:03:03 2015 +0530 afr: refresh inode using fstat Backport of http://review.gluster.org/12894 For fd based operations (fgetxattr, readv etc.) if an inode refresh is required, do so using fstat instead of lookup. This is because the file might have been deleted by another client before refresh but posix mandates that FOPS using already open fds must still succeed. Change-Id: Id5f71c3af4892b648eb747f363dffe6208e7ac09 BUG: 1290363 Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: http://review.gluster.org/13040 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu>
COMMIT: http://review.gluster.org/12939 committed in release-3.7 by Raghavendra G (rgowdapp) ------ commit 1a464c2ef3b8351e2d5217009d9a0a20e03add9a Author: Susant Palai <spalai> Date: Wed Dec 9 03:53:45 2015 -0500 storage/posix: fix dict leak in posix_fgetxattr BUG: 1290363 Change-Id: I49200316250b9894fdbf93ae33e50b02abb74db8 Reviewed-on: http://review.gluster.org/12916 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu> Signed-off-by: Susant Palai <spalai> Reviewed-on: http://review.gluster.org/12939 Reviewed-by: Raghavendra G <rgowdapp>
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.7.7, please open a new bug report. glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user