[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:35 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...
====================================================================== 

---------------------------------------------------------------------- 
 sruffell - 05-08-08 10:35  
---------------------------------------------------------------------- 
If rmmod can yank a module that is in use, then there is absolutely a
problem in the drivers, specifically with reference counts on the modules.

Actions in user space should never cause a kernel panic.  If they do it is
indicative of problems in kernel code.  Your suggestion above might indeed
mask a problem but does not fix the root cause.  What if it isn't asterisk
that has the module in use, but ztmonitor or another one of the utilities? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-08-08 10:35  sruffell       Note Added: 0086609                          
======================================================================