net: time the stall, not the wait, before dropping an unreadable peer

Found auditing the previous commit for the push. Timing from the first
rewind would drop a peer whose message is large and merely slow, which
would be a fault of our own making rather than one we fixed.

Restart the clock whenever the buffer has grown by even one byte since the
last look. A transfer still making progress is never dropped however long
it takes; only one that has stopped growing while the node goes on
expecting more is, which is the actual failure.

(cherry picked from commit 5dddb26bae02013ce87719b11953aadf0bfa2594)

0 files changed, 0 insertions, 0 deletions