> I tried this and it doesn't fix the issue in my test. It operates only > in IB_CM_ESTABLISHED but in my tests the order of operations in client > side is > 1. rdma_connect() was called > 2. lap was sent (for which apr will never be received - according to test > case) > 3. rdma_disconnect() was called
Let me think about the best way to handle this. We may want ib_send_cm_dreq() to cancel any outstanding LAP message. This should fix the destroy case as well, since it calls into disconnect. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
