[asterisk-bugs] [JIRA] (ASTERISK-22040) Remove the bridge pointer from ast_channel; refactor consumers of the bridge pointer to safely get it through bridge_channel

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett closed ASTERISK-22040.
--------------------------------------

    Resolution: Won't Fix
    
> Remove the bridge pointer from ast_channel; refactor consumers of the bridge pointer to safely get it through bridge_channel
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-22040
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22040
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Bridging
>    Affects Versions: 12
>            Reporter: Matt Jordan
>      Target Release: 12
>
>
> Unfortunately, we probably shouldn't have put the {{bridge}} pointer on the channel object. Channels can be moved around in the bridging system, and hence it isn't safe to access the {{bridge}} pointer on the channel without first locking the bridge.
> It is safe, however, to use the {{bridge_channel}} pointer.
> What is needed is a way to *ask* the bridging framework for a reference to the bridge that the channel happens to be in.
> {noformat}
> /* BUGBUG the bridge pointer must change to an ast_channel_bridge pointer because it will never change while the channel is in the bridging system whereas the bridge could change. */
> 	struct ast_bridge *bridge;                      /*!< Bridge this channel is participating in */
> {noformat}

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