DOC: server/threads: document which functions need to be called with/without locks
authorWilly Tarreau <w@1wt.eu>
Tue, 21 Aug 2018 09:54:26 +0000 (11:54 +0200)
committerWilly Tarreau <w@1wt.eu>
Tue, 21 Aug 2018 12:58:25 +0000 (14:58 +0200)
commit46b7f53ad957d9f9a44e69bf23382ffc9bab724c
treebad1c8d8caa562f089b92bcc4c4653bb53d7d62e
parenta275a3710eaa365150fe89e2e7a8fbdce87bb30e
DOC: server/threads: document which functions need to be called with/without locks

At the moment it's totally unclear while reading the server's code which
functions require to be called with the server lock held and which ones
grab it and cannot be called this way. This commit simply inventories
all of them to indicate what is detected depending on how these functions
use the struct server. Only functions used at runtime were checked, those
dedicated to config parsing were skipped. Doing so already has uncovered
a few bugs on some CLI actions.
src/server.c