[Bug] The handling of Socket EOF under Wisp is problematic

[yuleil]

Description
Continue reading socket after reading EOF:

• enable Wisp: SocketException("closed")
• disable Wisp: got eof(-1)

Steps to Reproduce
Steps to reproduce the behavior:

1. Save below snippet '...'
2. Compile it with javac '....'
3. Execute with VM options '....'
4. See error

Expected behavior
the behavior of reading a closed socket is consistent after switching wisp

JDK version
Dragonwell 8.4.4

Execution environment

• OS and version:
• CPU model:
• Number of CPU cores:
• Size of physical memory:
• Inside Linux container?
  • Linux container name (docker, pouch, etc):
  • Linux container version:

[yuleil]

import java.io.InputStream;
import java.net.ServerSocket;
import java.net.Socket;

public class A {

    public static void main(String[] args) throws Exception {
        ServerSocket serverSocket = new ServerSocket(0);
        Socket fd = new Socket("localhost", serverSocket.getLocalPort());
        /* 1. */ serverSocket.accept().close();
        InputStream is = fd.getInputStream();
        /* 2. */ is.read();
        /* 3. */ fd.close();
        /* 4. */ is.read();
    }
}

This is a piece of reproducing code. Note the first is.read() is required.