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

Matt Jordan (JIRA) noreply at issues.asterisk.org
Tue Mar 26 09:07:01 CDT 2013


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

Matt Jordan commented on ASTERISK-21162:
----------------------------------------

I went ahead and committed this in r383839 in Asterisk 1.8. I was able to reproduce the problem and, with the patch, the problem no longer occurs. Testing included using batches of 30 CDRs, triggered both by time delay as well as by accumulation of CDRs.

If you can test this as well to make sure this is resolved that'd be appreciated. If it isn't, just leave a comment here or contact a bug marshal in #asterisk-bugs (or e-mail me!) and I'll reopen this issue.
                
> 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: Chase Venters
>            Severity: Critical
>         Attachments: ASTERISK-21162-1.8.diff, 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: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list