REVIEW: http://review.gluster.org/11276 (glusterd: Removing sync lock and unlock inside rcu read critical section) posted (#2) for review on master by Anand Nekkunti (email@example.com)
REVIEW: http://review.gluster.org/11306 (glusterd: Removing sync lock and unlock inside rcu read critical section) posted (#1) for review on release-3.7 by Anand Nekkunti (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/11276 committed in master by Atin Mukherjee (email@example.com)
Author: anand <firstname.lastname@example.org>
Date: Wed Jun 17 16:11:48 2015 +0530
glusterd: Removing sync lock and unlock inside rcu read critical section
Issue : Glsuterd was crashing during peer probe.
RCA : In glusterd, we are using big lock which is implemented based on sync
task frame work for thread synchronization, sync task frame work swap the threads
if there is no worker pool threads available. Due to this rcu lock and rcu unlock
was happening in different threads (urcu-bp will not allow this), resulting into
fix : Removing sync lock and unlock inside rcu read critical section, which was left out by
Signed-off-by: anand <email@example.com>
Reviewed-by: Atin Mukherjee <firstname.lastname@example.org>
Reviewed-by: Krishnan Parthasarathi <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
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.