[asterisk-bugs] [Asterisk 0015862]: chan_sip deadlock in mutex sip_alloc

Wed Oct 7 15:06:07 CDT 2009

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15862 
====================================================================== 
Reported By:                zerohalo
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   15862
Category:                   Channels/chan_sip/General
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.26.2 
JIRA:                       SWP-209 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-09 08:14 CDT
Last Modified:              2009-10-07 15:06 CDT
====================================================================== 
Summary:                    chan_sip deadlock in mutex sip_alloc
Description: 
output of core show locks and backtrace from a forced crash attached.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015349 Deadlock in do_monitor() of chan_sip
====================================================================== 

---------------------------------------------------------------------- 
 (0112021) dvossel (administrator) - 2009-10-07 15:06
 https://issues.asterisk.org/view.php?id=15862#c112021 
---------------------------------------------------------------------- 
I'm marking this as related to issue
https://issues.asterisk.org/view.php?id=15349.  It appears that it may be
possible for the dialog list to loop forever which would explain why
find_call would never give up the dialog list lock. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-07 15:06 dvossel        Note Added: 0112021                          
======================================================================