[asterisk-bugs] [Zaptel 0010806]: Channel opening and unregistering race

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Oct 22 13:40:12 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10806 
====================================================================== 
Reported By:                Matti
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   10806
Category:                   zaptel (the module)
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     new
Zaptel Version:              SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 3052 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-23-2007 03:45 CDT
Last Modified:              10-22-2007 13:40 CDT
====================================================================== 
Summary:                    Channel opening and unregistering race
Description: 
Function zt_specchan_open can have a race condition with zt_chan_unreg
resulting in crashing of the program (Asterisk) or the whole computer
during the opening of a Zap device file.
====================================================================== 

---------------------------------------------------------------------- 
 Matti - 10-22-07 13:40  
---------------------------------------------------------------------- 
Channel access in interrupt context does not need a lock if the access is
done by the driver owning the channel.

Zaptel does not need a separate span lock and I don't see an advantage in
adding it, so I don't recommend it.

The crash possibility can be either
- a deadlock (e.g. spinlock held while sleeping) or
- an unprotected access that would lead to segfault/exit/fatal exception
in 
  interrupt (e.g. inconsistent value) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-22-07 13:40  Matti          Note Added: 0072380                          
======================================================================




More information about the asterisk-bugs mailing list