Version: 1
-Previous: 8f9ec6936595c32022c7779fff098916f342deb3
-Head: be2a2a44663282cda1a60e05c3b85275c732acc6
+Previous: 4209d9f562af570112b9f3e9ba6808e11388ee3b
+Head: a2aba33dbaed2156917645b82b68766ef2014558
Applied:
rstream-cnt: be2a2a44663282cda1a60e05c3b85275c732acc6
+ nonblock: a2aba33dbaed2156917645b82b68766ef2014558
Unapplied:
af-ib-conn: cf7b9e73d471477d4c7dff2592e5b0d3a7dea8ae
addrtype: 23a84fed89ba3f6b0eb63e5f8b37c0df504d0d3e
--- /dev/null
+Bottom: 7dce4c415b86085b4718701aa45fc9f061036ab1
+Top: 7dce4c415b86085b4718701aa45fc9f061036ab1
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2013-02-19 20:03:58 -0800
+
+rsocket: Fix resetting O_NONBLOCK after calling shutdown
+
+Shutdown switches an rsocket from nonblocking to blocking to
+ensure that all data has been sent. After completing all
+transfers, it should switch back to nonblocking; this handles
+partial shutdown situations, where only half the connection
+is shut down. However, the code uses the value of '1' to
+set the nonblocking flag, rather than O_NONBLOCK. Fix this.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+