[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-02-11 09:40 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0117993) skochen (reporter) - 2010-02-11 09:40
 https://issues.asterisk.org/view.php?id=16432#c117993 
---------------------------------------------------------------------- 
I know it's not a lot to go by, but we're now running the server in
question on version 1.4.26. The uptime just passed the two week mark.

So it might have been a change somewhere between 1.4.26 and 1.4.28. That's
a large window, though. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-11 09:40 skochen        Note Added: 0117993                          
======================================================================