[ofw] patch: [IBAL] Removing the ASSERT that can happen at user level.

[Fab Tillier]

Figure out why al_destroy_cep was called with a NULL h_al, and fix that.  Otherwise you'll go to the 'invalid' code flow and not free the CEP properly.

-Fab

From: ofw-bounces at lists.openfabrics.org [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of Tzachi Dar
Sent: Tuesday, August 31, 2010 8:21 AM
To: ofw at lists.openfabrics.org
Subject: [ofw] patch: [IBAL] Removing the ASSERT that can happen at user level.

Signed off by: xalex

Index: B:/users/tzachid/projinf9/trunk/core/al/user/ual_cm_cep.c
===================================================================
--- B:/users/tzachid/projinf9/trunk/core/al/user/ual_cm_cep.c                (revision 5850)
+++ B:/users/tzachid/projinf9/trunk/core/al/user/ual_cm_cep.c             (revision 5851)
@@ -382,9 +382,13 @@
                DWORD                                bytes_ret;

                AL_ENTER( AL_DBG_CM );
+
+#if DBG
+             if ( !h_al) {
+                             AL_PRINT(TRACE_LEVEL_ERROR ,AL_DBG_ERROR , ("h_al == NULL, probably because qp creation was failed.\n") );
+             }
+#endif

-              CL_ASSERT( h_al );
-
                cl_spinlock_acquire( &gp_cep_mgr->obj.lock );
                if( *p_cid < cl_ptr_vector_get_size( &gp_cep_mgr->cep_vector ) )
                {
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofw/attachments/20100831/99afacb8/attachment.html>