[asterisk-bugs] [Asterisk 0016847]: [patch] Deadlock between dahdi_exception and dahdi_indicate

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16847 
====================================================================== 
Reported By:                shin-shoryuken
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16847
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.6.1.14 
JIRA:                       SWP-927 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-02-16 15:16 CST
Last Modified:              2010-06-24 17:23 CDT
====================================================================== 
Summary:                    [patch] Deadlock between dahdi_exception and
dahdi_indicate
Description: 
I've encountered a deadlock situation between dahdi_exception and
dahdi_indicate, running Asterisk 1.6.1.6 (confirmed as well in 1.6.1.14) on
Debian Lenny x86_64.  Deadlock occurs roughly once a week, usually under
lower call volume (strangely enough).  The issue seems to arise mostly when
swapping between call-waiting lines on a DAHDI channel.
====================================================================== 

---------------------------------------------------------------------- 
 (0123833) alecdavis (manager) - 2010-06-24 17:23
 https://issues.asterisk.org/view.php?id=16847#c123833 
---------------------------------------------------------------------- 
As has been said on reviewboard, callwaiting_deadlock_trunk.diff.txt is not
the right way to fix the issue.

Currently callwaiting_deadlock_trunk.diff.txt avoids the deadlock, which
helps. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-24 17:23 alecdavis      Note Added: 0123833                          
======================================================================