[asterisk-bugs] [Asterisk 0018310]: [patch] hint state changes deadlock/race
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jan 5 17:11:40 UTC 2011
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: ready for testing
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: 2011-01-05 11:11 CST
======================================================================
Summary: [patch] 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.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0018165 [patch] hint state changes deadlock pro...
has duplicate 0018535 app_queue deadlocks if weight is set
======================================================================
----------------------------------------------------------------------
(0130214) one47 (reporter) - 2011-01-05 11:11
https://issues.asterisk.org/view.php?id=18310#c130214
----------------------------------------------------------------------
This might be a bit simplistic, but can someone check I am not being
utterly stupid:
At present, I believe that the context-lock is being used to protect the
'statecbs' list. 'statecbs' is managed in main/pbx.c, and is not referenced
anywhere else. Everywhere in main/pbx.c that 'statecbs' is referenced, the
hints-lock is held.
Is the hints lock therefore not sufficient to protect 'statecbs' so that
the context-lock is only held when the context-lock is specifically
needed???
I believe that the possible exception to this is where the dialplan is
being reloaded, and hints potentially created or destroyed. This will be
done from a thread that holds the context-lock while trying to grab and
release the hints lock; I cannot see that being a problem, but could be
wrong...
Thoughts please?
Issue History
Date Modified Username Field Change
======================================================================
2011-01-05 11:11 one47 Note Added: 0130214
======================================================================
More information about the asterisk-bugs
mailing list