[asterisk-bugs] [JIRA] (ASTERISK-30345) loader.c: Modules that decline to load cannot be reloaded
Joshua C. Colp (JIRA)
noreply at issues.asterisk.org
Thu Dec 8 17:25:51 CST 2022
[ https://issues.asterisk.org/jira/browse/ASTERISK-30345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua C. Colp updated ASTERISK-30345:
--------------------------------------
Assignee: N A
> loader.c: Modules that decline to load cannot be reloaded
> ---------------------------------------------------------
>
> Key: ASTERISK-30345
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-30345
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/General
> Affects Versions: 20.0.1
> Reporter: N A
> Assignee: N A
>
> Currently, if a module declines to load, dlclose() isn't called, as the module stays "registered" but not loaded. When trying to unload the module, loader.c currently whines that the module isn't loaded and then bails. This can be problematic because it makes it impossible to unload a module that never loaded in the first place, meaning that if a module is uploaded, the shared object module can't be reloaded without completely restarting Asterisk, since there are unclosed dlopen references.
> This fixes this by actually unloaded the module if an explicit request to do so is received, so that it can be loaded from scratch the next time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list