Description of problem:
if a service is not connected to glusterd because of some reason and by then if there is some message that has to be transferred through RPC, then the whole glusterd crashes as it rpc fails.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Connection failed. Please check if gluster daemon is operational.
glusterd should throw error without crashing.
REVIEW: http://review.gluster.org/13854 (glusterd/suncop: double free of frame stack) posted (#1) for review on master by mohammed rafi kc (email@example.com)
REVIEW: http://review.gluster.org/13854 (glusterd/syncop: double free of frame stack) posted (#2) for review on master by mohammed rafi kc (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/13854 committed in master by Jeff Darcy (email@example.com)
Author: Mohammed Rafi KC <firstname.lastname@example.org>
Date: Wed Mar 30 17:42:44 2016 +0530
glusterd/syncop: double free of frame stack
If rpc message from glusterd during brick op phase
fails without sending, then frame was freed from
the caller function and call back function.
Signed-off-by: Mohammed Rafi KC <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Jeff Darcy <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.8.0, please open a new bug report.
glusterfs-3.8.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.