REVIEW: http://review.gluster.org/11706 (quota/marker: contribution with list_del can cause mem corruption) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/11706 committed in master by Raghavendra G (rgowdapp) ------ commit 0acd0b45e5ee22eb5bb35c21093136b3b062744f Author: vmallika <vmallika> Date: Fri Jul 17 12:50:59 2015 +0530 quota/marker: contribution with list_del can cause mem corruption There is a possibility that contribution is removed twice from list during unlink operation (with hard links) or during rename operation Use list_del_init for a thread safe deltion of member from list Change-Id: Iff5e0c03cc8f0ed85da0db1739b84b695abf9ea6 BUG: 1244109 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/11706 Tested-by: Gluster Build System <jenkins.com> Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Krishnan Parthasarathi <kparthas> Reviewed-by: Raghavendra G <rgowdapp>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user