[asterisk-bugs] [Asterisk 0019403]: [patch] Call pickup deadlock in ast_do_masquerade

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19403 
====================================================================== 
Reported By:                one47
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19403
Category:                   Core/Channels
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.18 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-06-03 04:03 CDT
Last Modified:              2011-06-03 04:10 CDT
====================================================================== 
Summary:                    [patch] Call pickup deadlock in ast_do_masquerade
Description: 
Using *8 call pickup can readily cause a deadlock where ast_do_masquerade()
has a channel locked, when calling ast_channel_free() - ast_channel_free
requests the channels (channel list) lock, which breaks locking order
requirements and caused a deadlock.
====================================================================== 

---------------------------------------------------------------------- 
 (0135664) one47 (reporter) - 2011-06-03 04:10
 https://issues.asterisk.org/view.php?id=19403#c135664 
---------------------------------------------------------------------- 
I have attached a patch, which I am quite sure is wrong! It surely cannot
be safe to unlock the original channel during a masquerade, even if we
re-lock it immediately.

Can it?

I would prefer to be able to schedule the destruction of the channel, but
there does not seem to be any generic scheduler running that we can hook
into. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-06-03 04:10 one47          Note Added: 0135664                          
======================================================================