[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gluster-bugs
Subject:    [Bugs] [Bug 1633552] glusterd crash in regression build
From:       bugzilla () redhat ! com
Date:       2018-09-27 15:36:40
Message-ID: bug-1633552-371520-9lVI7KuQq9 () bugzilla ! redhat ! com
[Download RAW message or body]

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

Worker Ant <bugzilla-bot@gluster.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|POST                        |MODIFIED



--- Comment #2 from Worker Ant <bugzilla-bot@gluster.org> ---
COMMIT: https://review.gluster.org/21287 committed in release-5 by "Shyamsundar
Ranganathan" <srangana@redhat.com> with a commit message- glusterd: acquire
lock to update volinfo structure

Problem: With commit cb0339f92, we are using a separate syntask
for restart_bricks. There can be a situation where two threads
are accessing the same volinfo structure at the same time and
updating volinfo structure. This can lead volinfo to have
inconsistent values and assertion failures because of unexpected
values.

Solution: While updating the volinfo structure, acquire a
store_volinfo_lock, and release the lock only when the thread
completed its critical section part.

> BUG: bz#1627610
> Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

> Change-Id: I545e4e2368e3285d8f7aa28081ff4448abb72f5d
(cherry picked from commit 484f417da945cf83afdbf136bb4817311862a8d2)

fixes: bz#1633552

Change-Id: I545e4e2368e3285d8f7aa28081ff4448abb72f5d
Signed-off-by: Sanju Rakonde <srakonde@redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
Bugs mailing list
Bugs@gluster.org
https://lists.gluster.org/mailman/listinfo/bugs
[prev in list] [next in list] [prev in thread] [next in thread]