[asterisk-bugs] [Asterisk 0014468]: Deadlock between (MOH) ast_write on one end and local_hangup on other end (p->lock versus chan->lock_dont_use)

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14468 
====================================================================== 
Reported By:                davidw
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   14468
Category:                   Channels/chan_local
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 duplicate
Duplicate:                  13676
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-02-12 11:08 CST
Last Modified:              2009-02-12 12:02 CST
====================================================================== 
Summary:                    Deadlock between (MOH) ast_write on one end and
local_hangup on other end (p->lock versus chan->lock_dont_use)
Description: 
If an ast_write (in this specific case from music on hold) on one end of a
local channel races with local_hangup, on the other end, a deadlock can
arise in which the ast_write end holds chan->lock_dont_use and is waiting
for p->lock and the local-hangup end has p->lock and is looping on trying
to acquire chan->lock_dont_use.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0013676 channel get stuck on ast_queue_frame wh...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-12 12:02 file           Status                   resolved => closed  
======================================================================