[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:all-tabpanel ]

Pavel Troller updated ASTERISK-21128:
-------------------------------------

    Attachment: ASTERISK-21128-1.8-modified.diff

Thanks for your patch, Matt! It required two modifications, one to let it compile and second to prevent systematic crashes, but now it seems OK. I've installed it on three nodes of our network. Because the deadlocks are relatively rare, now we will have to wait for at least 14 days to see, whether it really helps. Attaching modified version of the patch.
                
> 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: 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