[Bugs] [Bug 1246121] Disperse volume : client glusterfs crashed while running IO
bugzilla at redhat.com
bugzilla at redhat.com
Thu Jul 23 16:36:59 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1246121
--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11752 committed in release-3.7 by Xavier
Hernandez (xhernandez at datalab.es)
------
commit 75d50eaba3fd7d24874ba8acc9a776c863a932e2
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>
Change-Id: I9af012e717493684b7cd7d1c63baf2fa401fb542
BUG: 1246121
Signed-off-by: Pranith Kumar K <pkarampu at redhat.com>
Reviewed-on: http://review.gluster.org/11752
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Xavier Hernandez <xhernandez at datalab.es>
--
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=mpL5Almtus&a=cc_unsubscribe
More information about the Bugs
mailing list