[asterisk-bugs] [DAHDI-linux 0014183]: sending a large number of calls to app_meetme causes kernel panic

Asterisk Bug Tracker noreply at bugs.digium.com
Tue Jan 27 20:54:54 CST 2009


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14183 
====================================================================== 
Reported By:                TerryWhelan
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   14183
Category:                   wct4xxp
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     closed
Target Version:             2.2.0
Resolution:                 open
Fixed in Version:           2.2.0
====================================================================== 
Date Submitted:             2009-01-06 13:19 CST
Last Modified:              2009-01-27 20:54 CST
====================================================================== 
Summary:                    sending a large number of calls to app_meetme causes
kernel panic
Description: 
On machine 1 create a dial file that calls machine 2 plays about 30 seconds
of test messages and hangup.  Create one of these every 5 seconds.  On
machine 2 put all incoming calls into a meetme conference.  After a couple
of hundred calls machine 2 kernel panics.  I have dialed in using SIP and
on the PRI.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014270 kernel panic on VMWare
====================================================================== 

---------------------------------------------------------------------- 
 (0098926) svnbot (reporter) - 2009-01-27 20:54
 http://bugs.digium.com/view.php?id=14183#c98926 
---------------------------------------------------------------------- 
Repository: dahdi
Revision: 5865

_U  linux/tags/2.1.0.4/
U   linux/tags/2.1.0.4/drivers/dahdi/dahdi-base.c
U   linux/tags/2.1.0.4/drivers/dahdi/dahdi_dynamic.c
U   linux/tags/2.1.0.4/drivers/dahdi/tor2.c
U   linux/tags/2.1.0.4/drivers/dahdi/wct1xxp.c
U   linux/tags/2.1.0.4/drivers/dahdi/wct4xxp/base.c
U   linux/tags/2.1.0.4/drivers/dahdi/wcte11xp.c
U   linux/tags/2.1.0.4/drivers/dahdi/wcte12xp/base.c
U   linux/tags/2.1.0.4/include/dahdi/kernel.h

------------------------------------------------------------------------
r5865 | sruffell | 2009-01-27 20:54:51 -0600 (Tue, 27 Jan 2009) | 28 lines

Merged revisions 5590,5811,5819 via svnmerge from 
https://origsvn.digium.com/svn/dahdi/linux/trunk

........
r5590 | tzafrir | 2008-12-19 04:39:31 -0800 (Fri, 19 Dec 2008) | 4 lines

Fix the safety check in tor2 to be for SPANS_PER_CARD

Thanks to Eugene Teo, in a from issue http://bugs.digium.com/view.php?id=13954 .

........
r5811 | sruffell | 2009-01-25 23:19:47 -0800 (Sun, 25 Jan 2009) | 7 lines

Ensure the channel is in a good state before placing it on the chans
arrays.
Also ensure that dahdi_receive holds the chan_lock while iterating over
the
chans array to prevent channels from entering or leaving the array while
the
interrupt handler is running.

Related to issue http://bugs.digium.com/view.php?id=14183 .

........
r5819 | sruffell | 2009-01-26 11:44:36 -0800 (Mon, 26 Jan 2009) | 3 lines

Manipulate the REGISTERED flag with atomic bitops now since the bit is set
outside the protection of any locks.

........

------------------------------------------------------------------------

http://svn.digium.com/view/dahdi?view=rev&revision=5865 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-27 20:54 svnbot         Checkin                                      
2009-01-27 20:54 svnbot         Note Added: 0098926                          
======================================================================




More information about the asterisk-bugs mailing list