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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Sep 1 19:16:21 CDT 2009


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-09-01 19:16 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.


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

---------------------------------------------------------------------- 
 (0109990) tilghman (administrator) - 2009-09-01 19:16
 https://issues.asterisk.org/view.php?id=14859#c109990 
---------------------------------------------------------------------- 
I've made a few more changes to this patch, since you tested, in order to
better ensure that some possible race conditions were solved.  Would you
mind testing this again (against trunk)?  There's a somewhat simple change
I can make to backport this to 1.6.1, but I want to ensure that this code
works well, first. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-01 19:16 tilghman       Note Added: 0109990                          
2009-09-01 19:16 tilghman       Status                   ready for review =>
ready for testing
======================================================================




More information about the asterisk-bugs mailing list