[asterisk-bugs] [JIRA] (ASTERISK-21128) Locking inversion when attempting to set caller ID while holding iaxsl lock causes deadlock

[Pavel Troller (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203548#comment-203548 ] 

Pavel Troller commented on ASTERISK-21128:
------------------------------------------

So, it's about 10 days since the patch has been deployed and since then, there was no deadlock on any of three and later four treated systems, even with increased frequency of calls, which were prone to making deadlocks before.
I think that the probability, that the patch is doing the right thing and doesn't do anything harmful, is high enough to consider it as verified and commit it.
Pavel
                
> Locking inversion when attempting to set caller ID while holding iaxsl lock causes deadlock
> -------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21128
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21128
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>            Reporter: Pavel Troller
>            Assignee: Pavel Troller
>         Attachments: AST-21128-11.diff, ASTERISK-21128-1.8.diff, ASTERISK-21128-1.8-modified.diff, locks.txt
>
>
> Systems running IAX2 trunks (either with trunk=yes or without it) freeze occasionally with typical symptoms of unreleased locks. The lock appears mostly during the call setup, it hasn't been observed during speech phase or call release. I never found it in 1.6 or less, it appears since 1.8. The newest system on which the problem was observed is indicated below. The only known way to restore functionality is to kill and restart Asterisk. A special debugging Asterisk build has been deployed to one of the sites and core show locks command applied during the deadlock. Its output is attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira