[asterisk-bugs] [Asterisk 0015523]: [patch] chan_dahdi deadlock heavy incomming traffic

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15523 
====================================================================== 
Reported By:                adomjan
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15523
Category:                   Channels/chan_dahdi
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0.9 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-07-17 13:37 CDT
Last Modified:              2009-08-17 17:44 CDT
====================================================================== 
Summary:                    [patch] chan_dahdi deadlock heavy incomming traffic
Description: 
I had deadlocks ~ 2-3 hours on high incomming ss7 calls. The deadlock
happend after the answer.
After I moved ast_setstate(ast, AST_STATE_UP); in area where the pvt is
locked in dahdi_answer() (like in chan_sip), and protected from the double
answer, I have not more deadlocks.

====================================================================== 

---------------------------------------------------------------------- 
 (0109188) russell (administrator) - 2009-08-17 17:44
 https://issues.asterisk.org/view.php?id=15523#c109188 
---------------------------------------------------------------------- 
It's not clear what this patch fixes.

Can you provide more information about what deadlock you saw?  What
threads and what locks were involved?  In what order were the locks being
used in the different threads that caused the deadlock?

Ideally, we would like to see output from the "core show locks" CLI
command after the deadlock has occurred.  To enable this command, Asterisk
needs to be compiled with DEBUG_THREADS. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-17 17:44 russell        Note Added: 0109188                          
2009-08-17 17:44 russell        Assigned To              rmudgett =>         
2009-08-17 17:44 russell        Status                   assigned => feedback
======================================================================