[asterisk-bugs] [Asterisk 0016432]: racecondition leading to deadlock in chan_local

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16432 
====================================================================== 
Reported By:                fnordian
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16432
Category:                   Channels/chan_local
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-528 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 230432 
Request Review:              
====================================================================== 
Date Submitted:             2009-12-11 10:12 CST
Last Modified:              2010-01-25 05:33 CST
====================================================================== 
Summary:                    racecondition leading to deadlock in chan_local
Description: 
Hi,

there's a race in chan_local between local_hangup and queuing a dtmf
(ast_senddigit ... local_queue_frame), which can cause hanging channels and
a hanging ast_senddigit.

This is possible because local_digit_*-functions assume that they were
called on an unlocked channel, which is not always the cases, e.g.
manager_play_dtmf uses a locked channel to call ast_senddigit. With this
wrong assumption, deadlock_avoidance code is not called.
====================================================================== 

---------------------------------------------------------------------- 
 (0117123) skochen (reporter) - 2010-01-25 05:33
 https://issues.asterisk.org/view.php?id=16432#c117123 
---------------------------------------------------------------------- 
Curiously, we're seeing this problem after a week of uptime, give or take a
few hours.

I don't see the link, but perhaps it will make sense to someone else?

(I was not able to test this on 1.4.29, because it burdens our customers
with some regressions that have popped up.) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-25 05:33 skochen        Note Added: 0117123                          
======================================================================