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 (firstname.lastname@example.org)
REVIEW: https://review.gluster.org/16666 (libglusterfs, dht, locks, glusterd: Coverity fixes) posted (#8) for review on master by Nigel Babu (email@example.com)
COMMIT: https://review.gluster.org/16666 committed in master by Shyamsundar Ranganathan (firstname.lastname@example.org)
Author: Nigel Babu <email@example.com>
Date: Sat Feb 18 14:02:30 2017 +0530
libglusterfs, dht, locks, glusterd: Coverity fixes
Fix up use after free bugs and dead code
Signed-off-by: Nigel Babu <firstname.lastname@example.org>
Smoke: Gluster Build System <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
Reviewed-by: Atin Mukherjee <firstname.lastname@example.org>
Reviewed-by: Shyamsundar Ranganathan <email@example.com>
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 , 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.