linux read返回0,read一个收到RST的socket会返回0？

研究muduo网络库，发现它在收到RST的包时触发可读事件，然后读的时候返回了0，然后关闭TCP连接。

但是读一个收到RST的socket不是应该返回-1，并且设置errno为ECONNRESET

20180115 12:57:41.647071Z 7171 TRACE printActiveChannels {8: IN HUP ERR } - EventLoop.cc:323

20180115 12:57:41.647075Z 7171 TRACE handleEventWithGuard 8: IN HUP ERR - Channel.cc:86

20180115 12:57:41.647082Z 7171 ERROR TcpConnection::handleError [EchoServer-0.0.0.0:2007#1] - SO_ERROR = 104 Connection reset by peer - TcpConnection.cc:426

20180115 12:57:41.647093Z 7171 TRACE handleClose fd = 8 state = kConnected - TcpConnection.cc:411

20180115 12:57:41.647096Z 7171 TRACE updateChannel fd = 8 events = 0 index = 1 - EPollPoller.cc:113

20180115 12:57:41.647102Z 7171 TRACE update epoll_ctl op = DEL fd = 8 event = { 8: } - EPollPoller.cc:181

20180115 12:57:41.647108Z 7171 INFO EchoServer - 192.168.0.106:33334 -> 192.168.0.106:2007 is DOWN - echo.cc:27

20180115 12:57:41.647113Z 7171 INFO TcpServer::removeConnectionInLoop [EchoServer] - connection EchoServer-0.0.0.0:2007#1 - TcpServer.cc:112

20180115 12:57:41.647122Z 7171 TRACE removeChannel fd = 8 - EPollPoller.cc:157

20180115 12:57:41.647142Z 7171 DEBUG ~TcpConnection TcpConnection::dtor[EchoServer-0.0.0.0:2007#1] at 0x1FE16E0 fd=8 state=kDisconnected - TcpConnection.cc:70

上面是Muduo打印出来的日志，可以看到确实是收到RST，但是为什么read会返回0了？看到很多资料都是read和write一个收到RST的socket都是返回-1，然后设置erno。

我的理解中只有收到FIN的socket，read才返回0，收到RST的socket会返回-1。