[asterisk-bugs] [JIRA] (ASTERISK-22093) Deadlock due to locking inversion between PBX context lock and channel lock while reloading dialplan through pbx_lua

[David Brillert (JIRA)]

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

David Brillert commented on ASTERISK-22093:
-------------------------------------------

We aren't using pbx_lua so I changed modules.conf so it won't load.
I hoped that would be enough to fix the problem but the gdb trace still doesn't look 'happy, happy, happy'.
The load gets crazy and I still see some <Address 0x6 out of bounds> that look like memory corruption in the gdb trace.
                
> Deadlock due to locking inversion between PBX context lock and channel lock while reloading dialplan through pbx_lua
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22093
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22093
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/PBX, PBX/pbx_lua
>    Affects Versions: 11.5.0
>            Reporter: David Brillert
>            Assignee: David Brillert
>            Severity: Critical
>         Attachments: 7_26_2013 gdb thread apply all bt full.txt, gdb thread apply all bt full.txt, gdb thread apply all bt.txt
>
>
> Third deadlock in two weeks.
> Asterisk not built with NOT_OPTIMIZED or thread debug options.
> The best I could do was attach GDB to Asterisk PID and get a thread apply all BT (attached)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira