mirror of
https://github.com/trapexit/mergerfs.git
synced 2026-10-26 19:01:56 -04:00
The CAS loop on _remove_count uses memory_order_relaxed for both success and failure, which is correct but non-obvious. Add a comment explaining that _remove_self acquires _threads_mutex immediately after the successful CAS, and that mutex acquisition provides the necessary happens-before edge between the scaling-side increment and the worker-side erase/detach. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| acutest | ||
| boost | ||
| CLI11 | ||
| fmt | ||
| khash | ||
| libfuse | ||
| nonstd | ||
| rapidhash | ||
| scope_guard | ||
| subprocess | ||