[asterisk-bugs] [Asterisk 0014859]: [patch] lock is not released on channel masquarade

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14859 
====================================================================== 
Reported By:                atis
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14859
Category:                   Functions/func_lock
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.19 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-08 10:39 CDT
Last Modified:              2009-07-20 10:50 CDT
====================================================================== 
Summary:                    [patch] lock is not released on channel masquarade
Description: 
Scenario: 

Queue -> Local channel -> answer_macro -> TRYLOCK -> bridge (masquarade)
-> TRYLOCK

First TRYLOCK creates lock correctly, but unlock is called outside of the
same thread, so it gives permission denied. Respectively lock remains even
if channel is dead or masqueraded, and second attempt to TRYLOCK gives
failure.


====================================================================== 

---------------------------------------------------------------------- 
 (0107961) lmadsen (administrator) - 2009-07-20 10:50
 https://issues.asterisk.org/view.php?id=14859#c107961 
---------------------------------------------------------------------- 
Feel free to reassign this back to me when there is a valid scenario for
reproducing this issue.

Or even better, if the reporter can test in their environment, that would
be the ideal. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-20 10:50 lmadsen        Note Added: 0107961                          
2009-07-20 10:50 lmadsen        Assigned To              lmadsen => tilghman 
2009-07-20 10:50 lmadsen        Status                   feedback => ready for
testing
======================================================================