Hey guys,
>> Do you still want me to bisect? Or should I wait? If you think the
>> problem is the same I'll just test the fix :-)
>
> Don't waste your time bisecting. I'll propose you to test the patch
> instead. The problem I've seen is always the same and is related to
> the fact that the SSL layer might have read all pending data from a
> socket but not delivered everything to the buffer by lack of space
> for example. Once the buffer is flushed and we want to read what
> follows, we re-enable polling. But there's no more data pending so
> poll() does not wake up the reader anymore. It happened to work due
> to the speculative polling we've been using a lot, but sometimes it
> was not intentional and caused some syscalls to be attempted for no
> reason (resulting in many EAGAIN in recvfrom). When fixing this, we
> also break what made SSL happen to work :-(
>
> I've been wanting for about 1 year to change the polling to include
> the status of the FD there (EAGAIN or not). But since it's complex
> and there were not many reasons for doing it, I preferred to delay.
> Now is a good opportunity given that I broke it several times in the
> last few weeks.
For the record:
Has this been fixed by commit 4afd70aea ("BUG/MAJOR: fix freezes during
compression") or is that a unrelated problem?
Thanks,
Lukas
