REVIEW: http://review.gluster.org/13249 (protocol/server: Fix memory corruption during client-table-expand.) posted (#1) for review on release-3.7 by Raghavendra G (rgowdapp@redhat.com)

COMMIT: http://review.gluster.org/13249 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu@redhat.com) 
------
commit 320f684a5eec9c6d39c674a93d48783301db5157
Author: Raghavendra G <rgowdapp@redhat.com>
Date:   Thu Jan 14 16:11:27 2016 +0530

    protocol/server: Fix memory corruption during client-table-expand.
    
    gf_client_clienttable_expand frees up old entries after expanding. So,
    cliententry should be reassigned to a free slot in new array of
    cliententries. Earlier it used to point to a slot in oldentries
    resulting in a use-after-free bug.
    
    Thanks to Pranith for the assistance provided.
    
    Change-Id: Iabe40c7df475471a7df7bccb302aef496ded3f1c
    BUG: 1299314
    Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
    Reviewed-on: http://review.gluster.org/13249
    Smoke: Gluster Build System <jenkins@build.gluster.com>
    CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>

Client crash was because of glibc issue tracked by bz 1027101 and bz 1305406.

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