[asterisk-bugs] [Asterisk 0017994]: [patch] crash in __ast_manager_event_multichan

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17994 
====================================================================== 
Reported By:                vrban
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   17994
Category:                   Core/ManagerInterface
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     feedback
Target Version:             1.8.0
Asterisk Version:           1.8.0-beta5 
JIRA:                       SWP-2244 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-09-15 02:59 CDT
Last Modified:              2010-10-12 10:58 CDT
====================================================================== 
Summary:                    [patch] crash in __ast_manager_event_multichan
Description: 
Hello, today i got this core. See gdb output in gdb.txt
====================================================================== 

---------------------------------------------------------------------- 
 (0127875) svnbot (reporter) - 2010-10-12 10:58
 https://issues.asterisk.org/view.php?id=17994#c127875 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 291227

U   branches/1.8/main/manager.c

------------------------------------------------------------------------
r291227 | dvossel | 2010-10-12 10:58:57 -0500 (Tue, 12 Oct 2010) | 16
lines

Fixes manager.c crash.

This issue was caused by improper use of the mansession lock and
manession_session lock.  These two structures are confusing to begin
with so I'm not surprised this occurred.  I fixed this by consistently
making sure we use each of these locks only to protect the data
in the corresponding structure.  We had mismatched usage of these
locks which resulted in no mutual exclusivity occurring at all.


(closes issue https://issues.asterisk.org/view.php?id=17994)
Reported by: vrban
Patches:
      mansession_locking_fix.diff uploaded by dvossel (license 671)
Tested by: vrban

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

http://svn.digium.com/view/asterisk?view=rev&revision=291227 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-12 10:58 svnbot         Checkin                                      
2010-10-12 10:58 svnbot         Note Added: 0127875                          
======================================================================