[asterisk-bugs] [Asterisk 0012689]: [patch] Posible deadlock: rwlock can't be recursively locked (writelocked)

noreply at bugs.digium.com noreply at bugs.digium.com
Tue May 20 08:54:32 CDT 2008


The following issue has been ASSIGNED. 
====================================================================== 
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:                     assigned
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:              
====================================================================== 
Date Submitted:             05-20-2008 08:52 CDT
Last Modified:              05-20-2008 08:54 CDT
====================================================================== 
Summary:                    [patch] Posible 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               
====================================================================== 
05-20-08 08:54  file           Assigned To               => murf            
======================================================================




More information about the asterisk-bugs mailing list