BUG/MAJOR: config: properly initialize cpu_map.thread[] up to MAX_THREADS
authorWilly Tarreau <w@1wt.eu>
Fri, 14 May 2021 06:26:38 +0000 (08:26 +0200)
committerWilly Tarreau <w@1wt.eu>
Fri, 14 May 2021 06:26:38 +0000 (08:26 +0200)
commit26f42a07793f7f5fa5dfee3421ded68a5c1284d9
tree97506f0c38d9a705ac6d1f44cf27f9ae0be569fa
parentcc9d9b0906ba3f8994a3107d95c646d3455598ac
BUG/MAJOR: config: properly initialize cpu_map.thread[] up to MAX_THREADS

A mistake was introduced in 2.4-dev17 by commit 982fb5339 ("MEDIUM:
config: use platform independent type hap_cpuset for cpu-map"), it
initializes cpu_map.thread[] from 0 to MAX_PROCS-1 instead of
MAX_THREADS-1 resulting in crashes when the two differ, e.g. when
building with USE_THREAD= but still with USE_CPU_AFFINITY=1.

No backport is needed.
src/haproxy.c