[asterisk-bugs] [Zaptel 0012606]: zaptel.init: Unloading kernel modules while asterisk has them in use can cause panic.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12606 
====================================================================== 
Reported By:                jfinstrom
Assigned To:                sruffell
====================================================================== 
Project:                    Zaptel
Issue ID:                   12606
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Zaptel Version:             1.4.10 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-08-2008 01:12 CDT
Last Modified:              05-08-2008 10:07 CDT
====================================================================== 
Summary:                    zaptel.init: Unloading kernel modules while asterisk
has them in use can cause panic.
Description: 
The init script will cause kernel modules to be forcibly removed while they
are in use. This is bad mojo and should not occur.

Suggest a condition be added to kill the unload if asterisk is running. 

Suggested edit below so it will need to be made a patch by someone who is
disclaimed, possibly with a more creative error...
====================================================================== 

---------------------------------------------------------------------- 
 jfinstrom - 05-08-08 10:07  
---------------------------------------------------------------------- 
A backtrace will not help as this is module agnostic. It happens with
multiple modules and cross vendor. This happens with non zaptel hardware
infact with the same method of removal. For some reason in Linux rmmod
module dies with an error module in use. When scripted the rmmod gains
magical voodoo powers and for some reason can yank the module anyway. I
don't care how the module is written or if some modules don't panic
regardless it is inappropriate to remove a module without stopping the
items that have it in use. I currently patch the init to reflect the above
changes. Not knowing the full range of cards which panic IMHO it is better
to set the code you do control to act appropriately rather than blowing it
off saying we should be able to do as we wish because its probably their
module anyway. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-08-08 10:07  jfinstrom      Note Added: 0086596                          
======================================================================