[asterisk-bugs] [JIRA] (ASTERISK-22857) Deadlock: Locked Here: chan_iax2.c line 9756 (socket_read)

[David M. Lee (JIRA)]

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

David M. Lee commented on ASTERISK-22857:
-----------------------------------------

David B.,

Richard's comment is a performance concern, but I would rather make sure we get a correct patch before we start optimizing it.

As far as committing it, that partially depends on whether it fixes your debug threads related deadlock or not :-)

I wrote the patch trying to correct some debug thread related deadlocks we were seeing on our CI servers. But the patch didn't fix the deadlocks we were seeing, so I've held off on committing it.

Your backtrace looks like the same sort of deadlock that this patch intends to fix. If the patch works for you, that's a good sign that it's correct and worth putting in. But if it doesn't I'll probably discard the code review since there would be something much more sneaky going on.
                
> Deadlock: Locked Here: chan_iax2.c line 9756 (socket_read)
> ----------------------------------------------------------
>
>                 Key: ASTERISK-22857
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22857
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: SVN, 11.6.0
>         Environment: 64 bit CentOS, 4GB RAM
>            Reporter: David Brillert
>            Assignee: David Brillert
>            Severity: Critical
>         Attachments: backtrace.txt, core show locks_gdb thread apply all bt full.txt, core show locks svn manual.txt, gdbcorebtbtfull.txt, iax2 debug.txt, valgrind.txt
>
>
> Full deadlock no call processing, no SIP traffic.
> GDB output DONT_OPTIMIZE DEBUG_THREADS BETTER_BACKTRACES thread apply all bt full.txt attached.  The deadlock occurred overnight while the system was idle.
> It is happening on multiple production servers.

--
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