Expose connect(2).

The new NET_FAILURE_RETRY in Posix.cpp is intended to replace the legacy one
in NetFd.h, but during the transition we need both. The new one also takes care
of the asynchronous Socket.close semantics, and changes the behavior when the
FileDescriptor is invalid on entry: that is now reported as EBADF; it's only
reported as "Socket closed" when we've been round the loop at least once,
giving us reason to believe the socket was ever open. Having had to debug this
distinction, I think the new semantics are less confusing.

Bug: 3107501
Change-Id: I243dc4fa2eddde7ba40e9b66ec8fc555bc4e80f9

1 files changed, 0 insertions, 5 deletions

diff --git a/dalvik/src/main/java/dalvik/system/BlockGuard.java b/dalvik/src/main/java/dalvik/system/BlockGuard.java
index 119833b..fd4be27 100644
--- a/dalvik/src/main/java/dalvik/system/BlockGuard.java
+++ b/dalvik/src/main/java/dalvik/system/BlockGuard.java
@@ -195,11 +195,6 @@ public final class BlockGuard {
             return mNetwork.writeDirect(fd, address, offset, count);
         }
 
-        public boolean connect(FileDescriptor fd, InetAddress inetAddress, int port) throws IOException {
-            BlockGuard.getThreadPolicy().onNetwork();
-            return mNetwork.connect(fd, inetAddress, port);
-        }
-
         public boolean isConnected(FileDescriptor fd, int timeout) throws IOException {
             if (timeout != 0) {
                 // Greater than 0 is a timeout, but zero means "poll and return immediately".