[asterisk-dev] [Code Review] Fix deadlock between subscription event RWLOCK and dialogs container lock in chan_sip. (simplified)
rmudgett
reviewboard at asterisk.org
Sat Nov 5 16:20:05 CDT 2011
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/1564/
-----------------------------------------------------------
(Updated Nov. 5, 2011, 4:20 p.m.)
Review request for Asterisk Developers, David Vossel and schmidts.
Changes
-------
Changed the name of dialogs_needdestroy to dialogs_to_destroy. It better reflects how it is used. It also removes possible confusion with the dialogs_needdestroy in Asterisk 10 branch which behaves differently.
Summary
-------
Timing between dialog destruction and a MWI event sending a message could result in a deadlock.
Order of events causing deadlock:
1a) The event subscription system calls the registered callbacks with its list RWLOCK held.
1b) The SIP monitor checks for dialogs needing destruction. It does an ao2_callback that holds the dialogs container lock while searching for dialogs to destroy.
2a) The event subscription SIP callback needs to create a temporary dialog to send out the MWI notification. That temporary dialog needs to be inserted in the dialogs container so it must wait.
2b) The dialog search finds a dialog to destroy and as a result releases the last reference for a peer. The peer destructor attempts to get the subscription RWLOCK but must wait.
3) deadlock
This is based off of the original diff posted for review: https://reviewboard.asterisk.org/r/1557/
It directly addresses the comment dvossel posted to the original diff of https://reviewboard.asterisk.org/r/1557/
This addresses bug ASTERISK-18747.
https://issues.asterisk.org/jira/browse/ASTERISK-18747
Diffs (updated)
-----
/branches/1.8/channels/chan_sip.c 343488
Diff: https://reviewboard.asterisk.org/r/1564/diff
Testing
-------
It compiles. :)
Thanks,
rmudgett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20111105/a2be1694/attachment.htm>
More information about the asterisk-dev
mailing list