Version: 1
-Previous: e3c858b2fb20fdea2b5e350a435da492871c54de
-Head: ac51c1095f505373a6ec54b8f1d990259fb34d97
+Previous: 730803fd4b54cc957dabe2dc0fd447b38caefd60
+Head: 10f8a3f709f58fda4072dbd847e9fe2e892a65f7
Applied:
real-close: 3409f8d6af187d25c63a5d1f8ee8bff5f14555e2
dup2: ca5813e7cf95dee5933fc417e4a34d26f2b01824
oobinline: ac51c1095f505373a6ec54b8f1d990259fb34d97
+ fork-connect: 10f8a3f709f58fda4072dbd847e9fe2e892a65f7
Unapplied:
dbg-out: 04273ee712db4d53efb390462c1b738bb54a57df
fstat: a62c653906870422edef5f6388dac9f76c953e35
--- /dev/null
+Bottom: 3ea2748a5c41b11a2e7033c56bddd938d2770b6c
+Top: 3ea2748a5c41b11a2e7033c56bddd938d2770b6c
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2012-08-10 21:44:39 -0700
+
+rspreload: Do not block connect when supporting fork
+
+Many FTP servers require fork support. However, FTP clients,
+such as ncftp, will perform the following call sequence:
+
+send PASV request to server over connection 1
+ server will listen for connection 2
+issue nonblocking connect to server
+send ACCEPT request to server over connection 1
+ server will accept connection 2
+
+The current fork support converts all nonblocking connect
+calls to blocking. The result is that the FTP client ends up
+blocked waiting for the server to accept the connection,
+which it will never do.
+
+Fix this by deferring the fork connection handling until the
+first socket call after connect.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+