There's a few memory issues that are classified high priority and some dead code floating around.
REVIEW: https://review.gluster.org/16666 (Fix coverity errors) posted (#7) for review on master by Nigel Babu (nigelb)
REVIEW: https://review.gluster.org/16666 (libglusterfs, dht, locks, glusterd: Coverity fixes) posted (#8) for review on master by Nigel Babu (nigelb)
COMMIT: https://review.gluster.org/16666 committed in master by Shyamsundar Ranganathan (srangana) ------ commit b584c068c6526853f82ccd2a406c3596d7d56be0 Author: Nigel Babu <nigelb> Date: Sat Feb 18 14:02:30 2017 +0530 libglusterfs, dht, locks, glusterd: Coverity fixes Fix up use after free bugs and dead code Change-Id: I8f79ed6b5108926c1fac31c147b5ecba79d10785 BUG: 1424905 Signed-off-by: Nigel Babu <nigelb> Reviewed-on: https://review.gluster.org/16666 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Shyamsundar Ranganathan <srangana>
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.11.0, please open a new bug report. glusterfs-3.11.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://lists.gluster.org/pipermail/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/