[asterisk-bugs] [Asterisk 0014859]: [patch] lock is not released on channel masquerade
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Sep 25 15:23:18 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: ready for testing
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-25 15:23 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.
======================================================================
----------------------------------------------------------------------
(0111388) tilghman (administrator) - 2009-09-25 15:23
https://issues.asterisk.org/view.php?id=14859#c111388
----------------------------------------------------------------------
Huh. I can't get it to crash at all. Are you running the latest 1.6.1
code from SVN?
Issue History
Date Modified Username Field Change
======================================================================
2009-09-25 15:23 tilghman Note Added: 0111388
======================================================================
More information about the asterisk-bugs
mailing list