REVIEW: https://review.gluster.org/16883 (glusterfsd+libglusterfs: add null checks during attach) posted (#1) for review on master by Jeff Darcy (jdarcy)
COMMIT: https://review.gluster.org/16883 committed in master by Vijay Bellur (vbellur) ------ commit 90b2b9b29f552fe9ab53de5c4123003522399e6d Author: Jeff Darcy <jdarcy> Date: Thu Mar 9 12:49:27 2017 -0500 glusterfsd+libglusterfs: add null checks during attach It's possible (though unlikely) that we could get a brick-attach request while we're not ready to process it (ctx->active not set yet). Add code to guard against this possibility, and return appropriate error indicators. Change-Id: Icb3bc52ce749258a3f03cbbbdf4c2320c5c541a0 BUG: 1430860 Signed-off-by: Jeff Darcy <jdarcy> Reviewed-on: https://review.gluster.org/16883 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Vijay Bellur <vbellur>
REVIEW: https://review.gluster.org/16651 (tests: add test for brick-daemon crash when glusterd restarted) posted (#2) for review on master by Jeff Darcy (jdarcy)
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/