Version: 1
-Previous: 187c029d6a3d7926f9545199c84f7a4f254dde42
-Head: a164a463c8afadc743d8a3c500bae39cb4d635cb
+Previous: 2e2a8242470c2008835892d9bec91a547a7de869
+Head: f4729165ed3410e5921d535f62db180c8012e6d7
Applied:
- rs-idm: 83ea10c26afa22b27d5b20510cdeaa09c581be91
- refresh-temp: a164a463c8afadc743d8a3c500bae39cb4d635cb
+ rs-idm: f4729165ed3410e5921d535f62db180c8012e6d7
Unapplied:
raccept-invalid: 8d5251952074622e8be0c9828d5eb573b4a1c6d2
old-af-ib: aaa0d9ca917c8c361a978e5a116963c2cceac5ba
+++ /dev/null
-Bottom: cc9fe9e0f61b120af8e519dd3c5c3802a7170a6e
-Top: cc9fe9e0f61b120af8e519dd3c5c3802a7170a6e
-Author: Sean Hefty <sean.hefty@intel.com>
-Date: 2015-02-10 16:51:19 -0800
-
-Refresh of rs-idm
-
----
-
-
overlap with the removal of an rsocket. This can result in
accessing freed memory.
-Problem reported by:
+Problem reported by: Sasha Kotchubievsky <sashakot@mellanox.com>
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
---