[asterisk-bugs] [Asterisk 0013839]: call processing deadlock with dialplan reload and ast_hint_state_changed
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jan 21 17:20:35 CST 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13839
======================================================================
Reported By: mcallist
Assigned To: file
======================================================================
Project: Asterisk
Issue ID: 13839
Category: Core/PBX
Reproducibility: random
Severity: major
Priority: normal
Status: assigned
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: 2008-11-04 15:57 CST
Last Modified: 2009-01-21 17:20 CST
======================================================================
Summary: call processing deadlock with dialplan reload and
ast_hint_state_changed
Description:
I had a dialplan reload hit while a state change was taking place. Looking
at core, it appears that the conlock was taken by
ast_merge_context_and_delete() and the hints lock was taken by
ast_hint_state_changed()
The hint state change eventually came to ast_hint_extension() which
attempts to grab conlock. In the mean time calls were stacking up. I
forced a Segfault to get a core file and dug in to get this information.
======================================================================
----------------------------------------------------------------------
(0098379) svnbot (reporter) - 2009-01-21 17:20
http://bugs.digium.com/view.php?id=13839#c98379
----------------------------------------------------------------------
Repository: asterisk
Revision: 169867
U branches/1.4/main/pbx.c
------------------------------------------------------------------------
r169867 | file | 2009-01-21 17:20:34 -0600 (Wed, 21 Jan 2009) | 4 lines
Read lock the contexts to maintain the locking order when we are notified
that the state of a device has changed.
(closes issue http://bugs.digium.com/view.php?id=13839)
Reported by: mcallist
------------------------------------------------------------------------
http://svn.digium.com/view/asterisk?view=rev&revision=169867
Issue History
Date Modified Username Field Change
======================================================================
2009-01-21 17:20 svnbot Checkin
2009-01-21 17:20 svnbot Note Added: 0098379
======================================================================
More information about the asterisk-bugs
mailing list