[asterisk-bugs] [Asterisk 0018310]: hint state changes deadlock/race
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Nov 17 04:44:07 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18310
======================================================================
Reported By: one47
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18310
Category: Core/PBX
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.6.2.14
JIRA: SWP-2541
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-11-15 12:19 CST
Last Modified: 2010-11-17 04:44 CST
======================================================================
Summary: hint state changes deadlock/race
Description:
VERY similar to https://issues.asterisk.org/view.php?id=18165, but this is a
different deadlock path, so I have
raised a separate report.
Thread 1: taskprocessor -> handle_statechange
Lock order = conlock, hints, hint, pvt
Thread 2: chan_sip.c: handle_request_do -> handle_response_notify
Lock order = pvt, conlock
Thread2 only gets into the conlock if STATECHANGEQUEUE is true, ie. there
are rapid state changes happening on a subscribed hint.
======================================================================
----------------------------------------------------------------------
(0128916) one47 (reporter) - 2010-11-17 04:44
https://issues.asterisk.org/view.php?id=18310#c128916
----------------------------------------------------------------------
Hi Stefan,
As far as I know, the data returned by ast_get_hint is only stored in the
dialplan, it is not copied into the hint container or hint objects, so it
is still necessary to use pbx_get_extension to get the list of
hinted/monitored devices attached to the extension/extension pattern.
I am attaching a patch which adds the back-off retry behaviour to the
handle_statechange code. This has survived our load-test overnight. It is
pretty crude, so perhaps a better programmer will be able to add some
finesse to the issue :)
Issue History
Date Modified Username Field Change
======================================================================
2010-11-17 04:44 one47 Note Added: 0128916
======================================================================
More information about the asterisk-bugs
mailing list