[asterisk-bugs] [Asterisk 0013839]: call processing deadlock with dialplan reload and ast_hint_state_changed

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13839 
====================================================================== 
Reported By:                mcallist
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   13839
Category:                   Core/PBX
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.19 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-11-04 15:57 CST
Last Modified:              2009-01-21 17:20 CST
====================================================================== 
Summary:                    call processing deadlock with dialplan reload and
ast_hint_state_changed
Description: 
I had a dialplan reload hit while a state change was taking place.  Looking
at core, it appears that the conlock was taken by
ast_merge_context_and_delete() and the hints lock was taken by
ast_hint_state_changed()  

The hint state change eventually came to ast_hint_extension() which
attempts to grab conlock.  In the mean time calls were stacking up.  I
forced a Segfault to get a core file and dug in to get this information.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-21 17:20 svnbot         Status                   assigned => resolved
2009-01-21 17:20 svnbot         Resolution               open => fixed       
======================================================================