tree a5c760c37013d45c268b95d319af75bd541c9039
parent c3981fc95978a6bc44264c1970181eadaf56d2e8
author Willy Tarreau <w@1wt.eu> 1461233565 +0200
committer Willy Tarreau <w@1wt.eu> 1461599047 +0200
encoding latin1

BUG/MEDIUM: channel: incorrect polling condition may delay event delivery

The condition to poll for receive as implemented in channel_may_recv()
is still incorrect. If buf->o is null and buf->i is slightly larger than
chn->to_forward and at least as large as buf->size - maxrewrite, then
reading will be disabled. It may slightly delay some data delivery by
having first to forward pending bytes, but may also cause some random
issues with analysers that wait for some data before starting to forward
what they correctly parsed. For instance, a body analyser may be prevented
from seeing the data that only fits in the reserve.

This bug may also prevent an applet's chk_rcv() function from being called
when part of a buffer is released. It is possible (though not verified)
that this participated to some peers frozen session issues some people
have been facing.

This fix should be backported to 1.6 and 1.5 to ensure better coherency
with channel_recv_limit().
(cherry picked from commit 93dc478a04485272c723c0e510450d00b3c345c3)
(cherry picked from commit 83732fc353756b8e3eb08dca7e1f377755dc92de)
[wt: in 1.5 channel_full returns the opposite from 1.6's channel_may_recv]