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 (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/11706 committed in master by Raghavendra G (email@example.com)
Author: vmallika <firstname.lastname@example.org>
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
Signed-off-by: vmallika <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Reviewed-by: Krishnan Parthasarathi <firstname.lastname@example.org>
Reviewed-by: Raghavendra G <email@example.com>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.