Version: 1
-Previous: 0d1cbcbf9274d6b13fdaa94ec6c49990052bacb5
-Head: aa237d85e8cb72dcc30165d284f6c54255341bcc
+Previous: 65c87673777c85582e405cf00b731723d6141b1d
+Head: b70160a50c9882e3feeaac67e83527e2205224bd
Applied:
rm-build: d6d2302f2d258fa2c07e55a2e124a9bdd75367a0
cm_listen_handler: 56372fe5e423b7238a4db99258c1493748c0a582
cm_poll: aa237d85e8cb72dcc30165d284f6c54255341bcc
+ cm-rej: b70160a50c9882e3feeaac67e83527e2205224bd
Unapplied:
old-bld-32: bd1bd1d366e3927b7646da33e243213a5d59c235
old-apphang: 7a6f7ff02c6035e54fc262414eb9484ea98018b9
--- /dev/null
+Bottom: 94ddedd44bd8ad0ecfff1ba0cd50383b2addafa8
+Top: 94ddedd44bd8ad0ecfff1ba0cd50383b2addafa8
+Author: U-AMR\MSHEFTY <MSHEFTY@mshefty-MOBL2.amr.corp.intel.com>
+Date: 2010-01-08 14:26:59 -0800
+
+ib/cm: fix handling of REJ in REQ_RCVD state
+
+If a REJ is received immediately after receiving a REQ,
+then a callback can be queued to the user for the REJ before
+the user has had a chance to see or process the REQ. The
+result is that the user will not have had a chance to set
+any context associated with the REQ, which can lead to a
+crash processing the REJ.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+