tree 0205721c05264586ad4956a3dcd0b42db8f6b7f4
parent 9c1e15d8cd1ca748915cbc75094daae67f17b56c
author Willy Tarreau <w@1wt.eu> 1510771109 +0100
committer Willy Tarreau <w@1wt.eu> 1510771385 +0100
encoding latin1

BUG/MAJOR: ebtree/scope: properly tag upper nodes during insertion

Christopher found a case where some tasks would remain unseen in the run
queue and would spontaneously appear after certain apparently unrelated
operations performed by the other thread.

It's in fact the insertion which is not correct, the node serving as the
top of duplicate tree wasn't properly updated, just like the each top of
subtree in a duplicate tree. This had the effect that after some removals,
the incorrectly tagged node would hide the underlying ones, which would
then suddenly re-appear once they were removed.

This is 1.8-specific, no backport is needed.