[asterisk-bugs] [DAHDI-linux 0015210]: dahdi_dynamic_loc crashes as soon as a valid span pair is activated

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15210 
====================================================================== 
Reported By:                mapacheco
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   15210
Category:                   dahdi_dynamic_loc
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-27 22:27 CDT
Last Modified:              2009-06-26 12:22 CDT
====================================================================== 
Summary:                    dahdi_dynamic_loc crashes as soon as a valid span
pair is activated
Description: 
Sample /etc/dahdi/system.conf:
dynamic=loc,1:0,24,0
dynamic=loc,1:1,24,0
bchan=1-23
dchan=24
bchan=25-47
dchan=48
mulaw=1-23,25-47
loadzone=us
defaultzone=us

modprobe dahdi_dummy
dahdi_cfg -v

My two systems get into a hard freeze (not even Alt-SysRq works), I
already debugged and found the root of the issue, see below.

If I comment all spinlock statements on dahdi_dynamic.c function
dahdi_dynamic_receive, then it doesn't freeze. The underlying cause for the
freeze we're having a recursive spinlock request, ztd_sendmessage calls
ztdlocal_transmit which calls dahdi_dynamic_receive with dlock spinlock
held.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-26 12:22 svnbot         Status                   assigned => resolved
2009-06-26 12:22 svnbot         Resolution               open => fixed       
======================================================================