[Bugs] [Bug 1243187] Disperse volume : client glusterfs crashed while running IO

[bugzilla at redhat.com]

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



--- Comment #5 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11670 committed in master by Xavier Hernandez
(xhernandez at datalab.es) 
------
commit 332cb6a6901c68f0c79070d7103cc7a728ea6d26
Author: Pranith Kumar K <pkarampu at redhat.com>
Date:   Wed Jul 15 06:16:54 2015 +0530

    cluster/ec: Handle race between unlock-timer, new lock

    Problem:
    New lock could come at the time timer is on the way to unlock. This was
leading
    to crash in timer thread because thread executing new lock can free up the
    timer_link->fop and then timer thread will try to access structures already
    freed.

    Fix:
    If the timer event is fired, set lock->release to true and wait for unlock
to
    complete.

    Thanks to Xavi and Bhaskar for helping in confirming that this race is the
RC.
    Thanks to Kritika for pointing out and explaining how Avati's patch can be
used
    to fix this bug.

    Change-Id: I45fa5470bbc1f03b5f3d133e26d1e0ab24303378
    BUG: 1243187
    Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
    Reviewed-on: http://review.gluster.org/11670
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6REQMe3Uv3&a=cc_unsubscribe