[asterisk-bugs] [JIRA] (ASTERISK-21162) Deadlock in cdr.c: cdr_batch_lock vs cdr_pending_lock

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-21162:
-----------------------------------------

I'm not a developer, but as a bug marshal part of what I do is make sure we have as much information as possible to save time for the developers who end up looking at the issue.

We do see issues, including deadlock scenarios that are near impossible to solve without the additional information provided by the compilation options mentioned. If the reporter is able to get it (most of the time they are) then it's best.

I understand the difficulty if the system is in production, and we really appreciate you reporting the issue in as detailed a fashion as you have. I'll go ahead and acknowledge this to get it on the core teams radar. If a developer responds back that we need any additional information then we'll comment here. Thanks!
                
> Deadlock in cdr.c: cdr_batch_lock vs cdr_pending_lock
> -----------------------------------------------------
>
>                 Key: ASTERISK-21162
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21162
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General
>    Affects Versions: 1.8.19.0
>         Environment: CentOS release 6.3 (Final)
> Linux ivr01.XXXXXXXX 2.6.32-279.22.1.el6.i686 #1 SMP Wed Feb 6 00:31:03 UTC 2013 i686 i686 i386 GNU/Linux
> Asterisk 1.8.19.0 from EPEL
>            Reporter: Chase Venters
>            Assignee: Rusty Newton
>            Severity: Critical
>         Attachments: deadlock_analysis.txt, gdb-asterisk-deadlock.zip
>
>
> I've run into a deadlock in Asterisk cdr.c. I have hundreds of threads blocked like this:
> [Edit by Rusty Newton - removed in-line trace analysis and attached as deadlock_analysis.txt]
> I think from looking at the 1.8.21.0-rc1 code that this issue still exists there.

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