[asterisk-bugs] [Asterisk 0019191]: [patch] deadlock in chan_sip

Asterisk Bug Tracker noreply at bugs.digium.com
Wed May 4 13:00:37 CDT 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19191 
====================================================================== 
Reported By:                byronclark
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19191
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.17.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-04-27 11:16 CDT
Last Modified:              2011-05-04 13:00 CDT
====================================================================== 
Summary:                    [patch] deadlock in chan_sip
Description: 
I've only seen this happen twice, both instances separated by about a
month.  
The only symptom is that Asterisk stops responding to SIP packets.

This time I ran 'pkill -11 asterisk' when it happened so I could get a
core dump. So, when looking at the backtrace, the segfault isn't the
problem.
====================================================================== 

---------------------------------------------------------------------- 
 (0134443) byronclark (reporter) - 2011-05-04 13:00
 https://issues.asterisk.org/view.php?id=19191#c134443 
---------------------------------------------------------------------- 
I'm assuming that it's safe to take the contexts lock when it will be taken
again by the same thread because it is a pthread_mutex_t and thus
recursive. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-04 13:00 byronclark     Note Added: 0134443                          
======================================================================




More information about the asterisk-bugs mailing list