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

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27909:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Deadlock in cdr.c: cdr_batch_lock vs cdr_pending_lock
> -----------------------------------------------------
>
>                 Key: ASTERISK-27909
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27909
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General
>    Affects Versions: 15.4.0
>         Environment: CentOS Linux 7 (Core)
> Linux *** 3.10.0-862.2.3.el7.x86_64 #1 SMP Wed May 9 18:05:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> Asterisk versions: 15.4.0
>            Reporter: Denis Lebedev
>
> We faced with deadlock in cdr.c in functions:
> {noformat}
> static int submit_scheduled_batch(const void *data)
> static void submit_unscheduled_batch(void)
> {noformat}
> Previously there was another deadlock which was fixed in ASTERISK-21162. That task added pretty the same mutex {{cdr_sched_lock}} on which asterisk is stucked in deadlock in consequent versions.
> The problem is quite rare so it's almost impossible to reproduce it under some artificial circumstances.
> Symptoms:
> * asterisk stops to flush cdr items into DB
> * begins to "eat" all memory on the host
> * but proceeds serving calls



--
This message was sent by Atlassian JIRA
(v6.2#6252)