Version: 1
-Previous: 515e0a99ea36fab0ff6fa519fd96a489d9ec9e63
-Head: 90b96504395c3e9f4652f4b46d63be3dea3689fe
+Previous: 0d6958a48c655602cb2b4e6ef29834821395e8ef
+Head: 6efa52c79449bcac31414f6682f87f9a30f05bae
Applied:
+ destroy_cqs: 6efa52c79449bcac31414f6682f87f9a30f05bae
Unapplied:
rs-qpsize: adee5db68a8f004ef5a94dc0cad94b74bf685088
rs-opts: 7c8fbc95903cf8f61422d7f2c58f83ba4f0b8ac4
--- /dev/null
+Bottom: 6bbc2f526b97dfafc16e7ec34dc8e4e1ce587f40
+Top: 6bbc2f526b97dfafc16e7ec34dc8e4e1ce587f40
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2012-05-20 22:41:38 -0700
+
+librdmacm: Check that send and recv CQs are different before destroying
+
+ucma_destroy_cqs() destroys both the send and recv CQs if they
+are non-null. If the two CQs are actually the same one, this
+results in a crash when trying to destroy the second CQ. Check
+that the CQs are different before destroying the second CQ.
+
+This fixes a crash when using rsockets, which sets the send and
+recv CQs to the same CQ.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+