epoll_wait2 fails to clear rnum or wnum
Brought to you by:
lilyco
When epoll_wait2 is used to wait for both readfds and writefds then if it returns because a socket is ready to write but there is no socket ready to read then rnum is not set to 0 but still has the value that it had before the call.
I fixed it by removing the !val->empty() check in the SET_RESULT macro used in epoll_wait2.
Guido