Hello, Steven Luo, on Wed 06 Apr 2016 17:00:50 -0700, wrote: > That said, sorecvoob() also calls soread(), so I'd guess we need to > deal with the possibility that soread() frees the socket in that case > as well?
Indeed, then sorecvoob() needs to return that information, so slirp_pollfds_poll can avoid doing anything else with this socket. > I could take care of this when I resend this patch series, if you > prefer. If you like, please do :) > I think this should be "might have been removed"? tcp_sockclosed() > doesn't seem to call tcp_close() in every case, so we can get -1 from > soread() without the socket being freed. Right. Samuel
