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

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Aug 18 06:45:21 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
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:                     feedback
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-08-18 06:45 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.


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

---------------------------------------------------------------------- 
 (0109205) atis (reporter) - 2009-08-18 06:45
 https://issues.asterisk.org/view.php?id=14859#c109205 
---------------------------------------------------------------------- 
Tilghman, Your patch seems to work. I see two errors when calling TRYLOCK,
but they don't seem to affect anything:

[2009-08-18 03:04:57.916] ERROR[13961] astobj2.c: bad magic number
0xdeadbeef for 0xb7b70610                                                  
                     [2009-08-18 03:04:57.916] ERROR[13961] astobj2.c: bad
magic number 0xdeadbeef for 0xb7b70610 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-18 06:45 atis           Note Added: 0109205                          
======================================================================




More information about the asterisk-bugs mailing list