← Back to context

Comment by HackerThemAll

11 hours ago

This is a blatant application bug, not an epoll issue, unless you prove otherwise.

It is a very, very easy mistake to make though. Nothing except edge-triggered I/O multiplexing makes it a problem not to read everything you possibly could, and it is often convenient to read less and let some other part of the code handle the rest. Forgot to call that part somehow? Oops, I/O on that socket is now screwed forever.