[asterisk-commits] rmudgett: branch 1.8 r375361 - /branches/1.8/channels/chan_dahdi.c
SVN commits to the Asterisk project
asterisk-commits at lists.digium.com
Mon Oct 29 10:49:28 CDT 2012
Author: rmudgett
Date: Mon Oct 29 10:49:22 2012
New Revision: 375361
URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=375361
Log:
chan_dahdi: Fix segfault dereferencing a NULL tech_pvt.
The tech support customer was using the AMI Redirect action shortly after
a call was placed. While the channel tried to do an ast_read(), the
masquerade resulting from the channel redirect took place. The masquerade
in the middle of the ast_read() resulted in the segfault.
(closes issue AST-1025)
Reported by: Trey Blancher
Patches:
jira_ast_1025_v1.8_v2.patch (license #5621) patch uploaded by rmudgett
Modified:
branches/1.8/channels/chan_dahdi.c
Modified: branches/1.8/channels/chan_dahdi.c
URL: http://svnview.digium.com/svn/asterisk/branches/1.8/channels/chan_dahdi.c?view=diff&rev=375361&r1=375360&r2=375361
==============================================================================
--- branches/1.8/channels/chan_dahdi.c (original)
+++ branches/1.8/channels/chan_dahdi.c Mon Oct 29 10:49:22 2012
@@ -8931,11 +8931,20 @@
CHANNEL_DEADLOCK_AVOIDANCE(ast);
/*
- * For PRI channels, we must refresh the private pointer because
- * the call could move to another B channel while the Asterisk
- * channel is unlocked.
+ * Check to see if the channel is still associated with the same
+ * private structure. While the Asterisk channel was unlocked
+ * the following events may have occured:
+ *
+ * 1) A masquerade may have associated the channel with another
+ * technology or private structure.
+ *
+ * 2) For PRI calls, call signaling could change the channel
+ * association to another B channel (private structure).
*/
- p = ast->tech_pvt;
+ if (ast->tech_pvt != p) {
+ /* The channel is no longer associated. Quit gracefully. */
+ return &ast_null_frame;
+ }
}
idx = dahdi_get_index(ast, p, 0);
More information about the asterisk-commits
mailing list