tree 2bf1aabe1b1f88b92edc9a4387783f48364d3269
parent f6715e788741e2bdb1c91ff381df8b8e63655c6b
author Willy Tarreau <w@1wt.eu> 1576822800 +0100
committer Willy Tarreau <w@1wt.eu> 1576839765 +0100
encoding latin1

MINOR: fd/threads: make _GET_NEXT()/_GET_PREV() use the volatile attribute

These macros are either used between atomic ops which cause the volatile
to be implicit, or with an explicit volatile cast. However not having it
in the macro causes some traps in the code because certain loop paths
cannot safely be used without risking infinite loops if one isn't careful
enough.

Let's place the volatile attribute inside the macros and remove them from
the explicit places to avoid this. It was verified that the output executable
remains exactly the same byte-wise.

(cherry picked from commit 337fb719ee93776cb399a333e04e2438427f0111)
Signed-off-by: Willy Tarreau <w@1wt.eu>
(cherry picked from commit d23e691a288316e9d96794e89e7248601b132d39)
Signed-off-by: Willy Tarreau <w@1wt.eu>