mirror of
https://github.com/trapexit/mergerfs.git
synced 2026-11-19 22:46:34 -05:00
The size check and _remove_count increment were not atomic — _threads_mutex was released between checking _threads.size() and incrementing _remove_count. A concurrent idle self-exit (which only holds _threads_mutex, not _scaling_mutex) could shrink the pool between the two operations, allowing _remove_count to signal a removal that would take the pool below min_allowed threads. Fix by holding _threads_mutex across both the size check and the _remove_count increment. The enqueue_unbounded call is kept outside the lock since it only needs to wake a worker and does not need to be atomic with the count check. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| acutest | ||
| boost | ||
| CLI11 | ||
| fmt | ||
| khash | ||
| libfuse | ||
| nonstd | ||
| rapidhash | ||
| scope_guard | ||
| subprocess | ||