[asterisk-bugs] [JIRA] (ASTERISK-29893) deadlock during bridge

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29893:
------------------------------------------

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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> deadlock during bridge
> ----------------------
>
>                 Key: ASTERISK-29893
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29893
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Bridges/bridge_builtin_features
>    Affects Versions: 18.9.0
>            Reporter: Pascal Cadotte Michaud
>
> With Asterisk 18.9.0 we have a dead lock that happened twice in 2 days.
> Given an incoming call from the operator
> Given a phone with a call forward
> When Dial the user's phone
> Then there's a deadlock
> After some debugging I've found that 2 threads were waiting in bridge_channel_internal_join. Each of the has a bridge_channel variable with a chan and it's peer referencing each other.
> After locking it's bridge and it ->chan both thread try to lock the peer which is already locked by the other thread.
> I think this bug has been introduced here https://gerrit.asterisk.org/c/asterisk/+/17543/2/main/bridge_channel.c#2861



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