[asterisk-bugs] [Asterisk 0016608]: [patch] Deadlock on &(&channels)->lock

Mon Mar 1 17:59:22 CST 2010

The following issue is now READY FOR TESTING. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16608 
====================================================================== 
Reported By:                sergee
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16608
Category:                   Channels/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                       SWP-732 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!): 237060 
Request Review:              
====================================================================== 
Date Submitted:             2010-01-14 15:04 CST
Last Modified:              2010-03-01 17:59 CST
====================================================================== 
Summary:                    [patch] Deadlock on &(&channels)->lock
Description: 
I've got 2 deadlocks in 3 days. It happens in a peak hours, with more then
a hundred calls in the system.

I've got 2 files 1 with "core show locks" - from the first deadlock (the
day before yesterday), second file - with output from gdb (intho thread,
thread apply all bt, thread apply all bt full) - from today's deadlock.
====================================================================== 

---------------------------------------------------------------------- 
 (0118724) tilghman (administrator) - 2010-03-01 17:59
 https://issues.asterisk.org/view.php?id=16608#c118724 
---------------------------------------------------------------------- 
Please test and verify that this patch prevents this situation from
occurring again. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-01 17:59 tilghman       Note Added: 0118724                          
2010-03-01 17:59 tilghman       Status                   feedback => ready for
testing
======================================================================