glusterd/snapshot: Don't release big_lock before completing snapshot creation

Releasing the big-lock can cause problem like deadlock or memory
corruption.

Same happened with bug 1091926 where glusterd on node-2 entered a commit
phase and released a big-lock.

The originator node received timeout for the commit phase and
triggered a post-validate cleanup to the node-2.

Now node-2 continued to work with the object that are alreday cleaned-up
and resulted in a crash.

Solution is to not to release big-lock in the commit phase of snapshot
creation.

Change-Id: I571194fdb0b0ecc91bd13f2a9fc92fe4338d14dc
BUG: 1091926
Signed-off-by: Vijaikumar M <vmallika@redhat.com>
Reviewed-on: http://review.gluster.org/7579
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Rajesh Joseph <rjoseph@redhat.com>
Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>

0 files changed, 0 insertions, 0 deletions