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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Sep 29 23:35:21 CDT 2009


The following issue has been ASSIGNED. 
====================================================================== 
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:                     assigned
Target Version:             1.6.0.16
Asterisk Version:           SVN 
JIRA:                        
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-09-29 23:35 CDT
====================================================================== 
Summary:                    [patch] lock is not released on channel masquerade
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.


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

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-29 23:35 svnbot         Status                   ready for testing =>
assigned
======================================================================




More information about the asterisk-bugs mailing list