tree a92bb61e85566dd1c3c612c8ec54fa2b99f21bb1
parent a5d7d07461db4de7cb4f3b4af15260ad4bc52927
author Willy Tarreau <w@1wt.eu> 1430769478 +0200
committer Willy Tarreau <w@1wt.eu> 1435053481 +0200
encoding latin1

BUG/MEDIUM: config: properly compute the default number of processes for a proxy

Chad Lavoie reported an interesting regression caused by the latest
updates to automatically detect the processes a peers section runs on.
It turns out that if a config has neither nbproc nor a bind-process
statement and depending on the frontend->backend chaining, it is possible
to evade all bind_proc propagations, resulting in assigning only ~0UL (all
processes, which is 32 or 64) without ever restricting it to nbproc. It
was not visible in backends until they started to reference peers sections
which saw themselves with 64 processes at once.

This patch addresses this by replacing all those ~0UL with nbits(nbproc).
That way all "bind-process" settings *default* to the number of processes
defined in nbproc instead of 32 or 64.

This fix could possibly be backported into 1.5, though there is no indication
that this bug could have any effect there.
(cherry picked from commit e428b08ee72879072897d1bcfa38589b7d1a89a5)