tree c4e43fa863f2ccb317f0147e409cde53bb1eca2b
parent 54907bb848962cc89d18fffb40af32010e4090b0
author Willy Tarreau <w@1wt.eu> 1576822800 +0100
committer Willy Tarreau <w@1wt.eu> 1576825768 +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.