https://sourceware.org/bugzilla/show_bug.cgi?id=26125
--- Comment #5 from Frank Ch. Eigler <fche at redhat dot com> --- Yeah, I suppose there is that race possibility. One way to fix it is to use something like file locks, such as a flock(2) on a designated file such as $CACHE/cache_clean_interval_s. During aging/cleanup, hold a LOCK_EX. During normal operation (creation of build-id subdirectories & files), hold a LOCK_SH to permit multiple clients to work independently of one another. -- You are receiving this mail because: You are on the CC list for the bug.
