Version: 1
-Previous: a937c02e3e54b740c4e9ecb039ec14fed0475662
-Head: ec6a8efe211b0dc98548443c2e0d67e2c355351f
+Previous: 983b69db2c78849074cce8335270ae54dead48e5
+Head: a0d5a8797de32a12cdc1e51aef332db25f8eef64
Applied:
rs-locking: ec6a8efe211b0dc98548443c2e0d67e2c355351f
+ reuseaddr: a0d5a8797de32a12cdc1e51aef332db25f8eef64
Unapplied:
comp_locks: b89aab130b4619806557e11e6b9c10964f00743f
preload: 5dfe7abc07064485c5100e04e5412279244c2bc3
--- /dev/null
+Bottom: 3fcdf48082614bb29c44242534cfeecb47e07114
+Top: 3fcdf48082614bb29c44242534cfeecb47e07114
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2012-05-10 11:17:32 -0700
+
+librdmacm/rsocket: Succeed setsockopt REUSEADDR on connected sockets
+
+The RDMA CM fail calls to set REUSEADDR on an rdma_cm_id if
+it is not in the idle state. As a result, this causes a failure
+in NetPipe when is run with socket calls intercepted by rsockets.
+Fix this by returning success when REUSEADDR is set on an rsocket
+that has already been connected. When running over IB, REUSEADDR
+is not necessary, since the TCP/IP addresses are mapped.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+