tree 5aabd51c3e726936da14f131fed23ddf437a91a6
parent 54ff9c339ddd5a808bf261ccec85791e5bcc18c5
author Willy Tarreau <w@1wt.eu> 1659625221 +0200
committer Willy Tarreau <w@1wt.eu> 1660323169 +0200
encoding latin1

BUG/MINOR: ring/cli: fix a race condition between the writer and the reader

The ring's CLI reader unlocks the read side of a ring and relocks it for
writing only if it needs to re-subscribe. But during this time, the writer
might have pushed data, see nobody subscribed hence woken nobody, while
the reader would have left marking that the applet had no more data. This
results in a dump that will not make any forward progress: the ring is
clogged by this reader which believes there's no data and the writer
will never wake it up.

The right approach consists in verifying after re-attaching if the writer
had made any progress in between, and to report that another call is
needed. Note that a jump back to the beginning would also work but here
we provide better fairness between readers this way.

This needs to be backported to 2.2. The applet API needed to signal the
availability of new data changed a few times since then.

(cherry picked from commit b8e0fb97f339583148446711ba69880b32105c7f)
Signed-off-by: Willy Tarreau <w@1wt.eu>
(cherry picked from commit 00f5c61a988de84a42810e2c164135abbcef0951)
[wt: s/ctx->ofs/ctx.cli.o0/; s/applet_have_no_more_data/si_rx_endp_done/;
     s/applet_have_more_data/si_rx_endp_more/]
Signed-off-by: Willy Tarreau <w@1wt.eu>
(cherry picked from commit 764717ad1b0831c2adb329e99ae3595d3ab1acca)
Signed-off-by: Willy Tarreau <w@1wt.eu>