[asterisk-bugs] [DAHDI-linux 0018422]: [patch] dahdi-base locks channel-exporting module in kernel if channel open fails

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Dec 6 22:48:52 CST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18422 
====================================================================== 
Reported By:                avarvit
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   18422
Category:                   dahdi (the module)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2010-12-03 23:21 CST
Last Modified:              2010-12-06 22:48 CST
====================================================================== 
Summary:                    [patch] dahdi-base locks channel-exporting module in
kernel if channel open fails
Description: 
If chan->span->ops->open() fails, then DAHDI_FLAGBIT_OPEN never
gets set and module_put is never called on the exporter module.


====================================================================== 

---------------------------------------------------------------------- 
 (0129379) avarvit (reporter) - 2010-12-06 22:48
 https://issues.asterisk.org/view.php?id=18422#c129379 
---------------------------------------------------------------------- 
Hi sruffel,
I took a look at your patch (without trying it) and it looks
good. It seems that, in comparison to what I originally
posted, you have just added a temp variable "ops" to hold
the channel's span ops; other than that, the patch looks
identical to my originally posted code.

There is no need for me to submit a patch of "my own". Yes,
it's fine if you put my real name and email in the patch
you have produced. Thanks for taking immediate action on
the issue! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-06 22:48 avarvit        Note Added: 0129379                          
======================================================================




More information about the asterisk-bugs mailing list