[asterisk-bugs] [Zaptel 0012606]: zaptel.init: Unloading kernel modules while asterisk has them in use can cause panic.
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu May 8 11:14:11 CDT 2008
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 11:14 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 11:14
----------------------------------------------------------------------
rmmod from a cli fails. Some reason the same failure does not occur when
init calls it. I cant figure out why its more aggressive. The kernel devs
do say if you yank a kernel module plan on reboot as it may panic.
Obviously we cant rewrite the kernel. I am not sure of the purpose of auto
yanking files anyway maybe the alternative is to only touch what you own.
Currently the init script yanks modules in proc modules. So rather than the
IF have it try to simply remove zaptel.ko and fail if it's in use. So
basically if you only touch the code you own and it craps then it can very
easily be filed as "not our problem" when you dynamically pull stuff out
you don't control then its your fault for touching things that aren't
yours.
Issue History
Date Modified Username Field Change
======================================================================
05-08-08 11:14 jfinstrom Note Added: 0086617
======================================================================
More information about the asterisk-bugs
mailing list