[asterisk-bugs] [Asterisk 0017188]: lack of locking in dahdi_request()

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Apr 15 11:22:08 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17188 
====================================================================== 
Reported By:                gknispel_proformatique
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17188
Category:                   Channels/chan_dahdi
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 257341 
Request Review:              
====================================================================== 
Date Submitted:             2010-04-15 09:05 CDT
Last Modified:              2010-04-15 11:22 CDT
====================================================================== 
Summary:                    lack of locking in dahdi_request()
Description: 
In dahdi_request(), iflist / ifend are acceded without any lock taken -- or
alternatively pri->crvs / pri->crvend are.

I don't know if/when those can be modified, especially regarding crv. For
iflist/ifend, maybe reloads are concerned, and also pseudo channels, which
I don't know what they are used for.
====================================================================== 

---------------------------------------------------------------------- 
 (0120474) gknispel_proformatique (reporter) - 2010-04-15 11:22
 https://issues.asterisk.org/view.php?id=17188#c120474 
---------------------------------------------------------------------- 
Some code review. I don't think this could cause a real issue *for me* so I
don't plan to try to trigger this potential issue on a test plateform.

I leave it to others to evaluate if this could cause a real world issue. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-15 11:22 gknispel_proformatiqueNote Added: 0120474                      
   
======================================================================




More information about the asterisk-bugs mailing list