REVIEW: http://review.gluster.org/8659 (cluster/dht: fix memory corruption in locking api.) posted (#2) for review on master by Raghavendra G (rgowdapp)
COMMIT: http://review.gluster.org/8659 committed in master by Vijay Bellur (vbellur) ------ commit ed4a754f7b6b103b23b2c3e29b8b749cd9db89f3 Author: Raghavendra G <rgowdapp> Date: Tue Sep 9 11:33:14 2014 +0530 cluster/dht: fix memory corruption in locking api. <man 3 qsort> The contents of the array are sorted in ascending order according to a comparison function pointed to by compar, which is called with two arguments that "point to the objects being compared". </man 3 qsort> qsort passes "pointers to members of the array" to comparision function. Since the members of the array happen to be (dht_lock_t *), the arguments passed to dht_lock_request_cmp are of type (dht_lock_t **). Previously we assumed them to be of type (dht_lock_t *), which resulted in memory corruption. Change-Id: Iee0758704434beaff3c3a1ad48d549cbdc9e1c96 BUG: 1139506 Signed-off-by: Raghavendra G <rgowdapp> Reviewed-on: http://review.gluster.org/8659 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Shyamsundar Ranganathan <srangana> Reviewed-by: Vijay Bellur <vbellur>
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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user