[asterisk-bugs] [Asterisk 0019025]: Conversion of hints to AO2 may changes locking order
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Mar 25 05:06:27 CDT 2011
The following issue has been SUBMITTED.
======================================================================
https://issues.asterisk.org/view.php?id=19025
======================================================================
Reported By: one47
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 19025
Category: Core/PBX
Reproducibility: N/A
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.6.2.18-rc1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-03-25 05:06 CDT
Last Modified: 2011-03-25 05:06 CDT
======================================================================
Summary: Conversion of hints to AO2 may changes locking order
Description:
Potential deadlock due to locking order change.
BEFORE the AO2 conversion, pbx.c would always grab the conlock before
grabbing the hints lock.
SINCE the conversion, the conlock is not grabbed directly at-all, and the
hints lock it the top-level lock for handling state change notifications.
Incidentally, while sending notifications, the conlock is grabbed to be
able to read the "hint" values from the dialplan. This gives an implied
locking order of hints and then conlock.
pbx.c currently says that the opposite is true.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2011-03-25 05:06 one47 New Issue
2011-03-25 05:06 one47 Asterisk Version => 1.6.2.18-rc1
2011-03-25 05:06 one47 Regression => No
2011-03-25 05:06 one47 SVN Branch (only for SVN checkouts, not tarball
releases) => N/A
======================================================================
More information about the asterisk-bugs
mailing list