Hide Forgot
Created attachment 526640 [details] Proposed patch Description of problem: This patch resolves a deadlock between the serialize lock (in exec/main.c) and the timer lock (in exec/timer.c). I observed this deadlock happening fairly quickly on a cluster using the EVT service from OpenAIS. (OpenAIS 1.1.4, Corosync 1.4.1) In prioritized_timer_thread(), it was grabbing: 1) timer lock 2) serialize lock In another thread, you have: 1) grab the serialize lock in deliver_fn() of exec/main.c 2) grab the timer lock in corosync_timer_add_duration(). The patch just swaps the locking order in the timer thread. Version-Release number of selected component (if applicable): 1.4.1
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause Using EVT service from OpenAIS. Consequence Sometimes (it's race so really depend on many things like number of cores, load, scheduler, ...) corosync deadlocks. Fix Change order of locking. Result Corosync doesn't deadlocks any longer.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0777.html