[asterisk-bugs] [Asterisk 0012689]: [patch] Possible deadlock: rwlock can't be recursively locked (writelocked)
noreply at bugs.digium.com
noreply at bugs.digium.com
Mon Jun 16 15:37:01 CDT 2008
The following issue has been RESOLVED.
======================================================================
http://bugs.digium.com/view.php?id=12689
======================================================================
Reported By: ys
Assigned To: murf
======================================================================
Project: Asterisk
Issue ID: 12689
Category: PBX/General
Reproducibility: always
Severity: minor
Priority: normal
Status: resolved
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 117261
Disclaimer on File?: N/A
Request Review:
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 05-20-2008 08:52 CDT
Last Modified: 06-16-2008 15:37 CDT
======================================================================
Summary: [patch] Possible deadlock: rwlock can't be
recursively locked (writelocked)
Description:
I found, that some thread libs, block thread if one rwlock are locked
twice. But some libs have "Resource deadlock avoided" decision.
This situation present if called __ast_context_destroy() function
(main/pbc.c).
In this function, context is locked and called
ast_context_remove_extension2() function, there context is locked again.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
06-16-08 15:37 svnbot Status assigned => resolved
06-16-08 15:37 svnbot Resolution open => fixed
======================================================================
More information about the asterisk-bugs
mailing list