[asterisk-bugs] [Zaptel 0010601]: Function zt_register should get a Linux 2.6 module and zt_unregister put

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Apr 1 10:10:26 CDT 2008


The following issue requires your FEEDBACK. 
====================================================================== 
http://bugs.digium.com/view.php?id=10601 
====================================================================== 
Reported By:                Matti
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   10601
Category:                   zaptel (the module)
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Zaptel Version:              SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 2810 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-30-2007 00:40 CDT
Last Modified:              04-01-2008 10:10 CDT
====================================================================== 
Summary:                    Function zt_register should get a Linux 2.6 module
and zt_unregister put
Description: 
Function zt_register should get a and function zt_unregister put a Linux
2.6 module. Module zaptel can call functions of registered modules and it
would be cleaner if zaptel itself took care of the modules not unloading
and leaving stale function pointers.
====================================================================== 

---------------------------------------------------------------------- 
 tzafrir - 04-01-08 10:10  
---------------------------------------------------------------------- 
First-off, I don't understand how the patches are related to the topic of
the bug report. I also believe that they allow hanging rmmod forever under
certain circumstances. Maybe open a separate bug for those if that is a
valid issue?

The topic of the bug report is a valid issue. xpp currently handles it
explicitly by maintaining open counts for channels. Before that was done,
incorrect removal caused Asterisk to crash in nice ways.

I'm not sure exactly how other modules handle this, if at all. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-01-08 10:10  tzafrir        Note Added: 0084846                          
04-01-08 10:10  tzafrir        Status                   new => feedback     
======================================================================




More information about the asterisk-bugs mailing list