mergerfs/vendored
Antonio S. Musumeci 65e136c667 Document why relaxed ordering is correct for _remove_count CAS
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>
2026-04-10 13:41:06 -04:00
..
acutest Update vendored/acutest to latest master 2026-03-02 01:09:16 -05:00
boost Update vendored/boost to 1.90.0 2026-03-02 01:09:16 -05:00
CLI11 Update vendored/CLI11 to v2.6.2 2026-03-02 01:09:16 -05:00
fmt Move fmtlib to vendored and upgrade to 12.1.0 2026-03-02 01:09:16 -05:00
khash Move 3rd party libraries to "vendored" directory 2026-03-02 01:09:16 -05:00
libfuse Document why relaxed ordering is correct for _remove_count CAS 2026-04-10 13:41:06 -04:00
nonstd Update vendored/nonstd to latest and fix API usage 2026-03-02 01:09:16 -05:00
rapidhash Update vendored/rapidhash to v3 2026-03-02 01:09:16 -05:00
scope_guard Move scope_guard to vendored/ 2026-03-24 21:13:34 -04:00
subprocess Update vendored/subprocess to v2.5 2026-03-02 01:09:16 -05:00