[Bugs] [Bug 1216942] glusterd crash when snapshot create was in progress on different volumes at the same time - job edited to create snapshots at the given time

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1216942



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10432 committed in release-3.7 by Vijay
Bellur (vbellur at redhat.com) 
------
commit 7bafeda4641582b5254f0e1f49e853dd87fe93f5
Author: anand <anekkunt at redhat.com>
Date:   Fri Apr 17 14:19:46 2015 +0530

    libglusterfs: Implementation of sync lock as recursive lock to avoid crash.

    Problem : In glusterd,we are using big lock which is implemented based on
sync
    task frame work for thread synchronization and rcu lock for data
consistency.
    sync task frame work swap the threads  if there is no worker poll threads
    available,due to this rcu lock and rcu unlock was happening in different
threads
    (urcu-bp will not allow this),resulting into glusterd crash.

    fix : To avoid releasing the sync lock(big lock) in between rcu critical
    section,implemented sync lock as recursive lock.

    More details:
    link : http://www.spinics.net/lists/gluster-devel/msg14632.html

    Change-Id: I2b56c1caf3f0470f219b1adcaf62cce29cdc6b88
    BUG: 1216942
    Signed-off-by: anand <anekkunt at redhat.com>
    Reviewed-on: http://review.gluster.org/10285
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Vijay Bellur <vbellur at redhat.com>
    (cherry picked from commit ada6b3a8800867934af57a57d5312f5a5d8374f0)
    Reviewed-on: http://review.gluster.org/10432
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Tested-by: Vijay Bellur <vbellur at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.