Skip to content
Browse files

cmake: atomic rename to fix toolchain cache creation race

While this race seems unlikely and harmless let's play it safe and
implement the usual solution: temporary file + atomic rename.

The race is unlikely and maybe even harmless because:

- Only sanitycheck seems to invoke cmake concurrently.
- Users rarely delete their ~/.cache/zephyr/ToolchainCapabilityDatabase/
- All concurrent cmake processes write the same, single byte to the same
- Creating a single byte is at least very fast, so extremely short
  window for others to read an empty file.

For additional background see links in issue #9992

Signed-off-by: Marc Herbert <>
  • Loading branch information...
marc-hb authored and nashif committed Apr 2, 2019
1 parent 3061c92 commit f098b44a1a5efe50ee6fc1fd5c67470837c342b3
Showing with 21 additions and 1 deletion.
  1. +21 −1 cmake/extensions.cmake
@@ -679,11 +679,31 @@ function(zephyr_check_compiler_flag lang option check)

# Populate the cache
if(NOT (EXISTS ${key_path}))

# This is racy. As often with race conditions, this one can easily be
# made worse and demonstrated with a simple delay:
# execute_process(COMMAND "sleep" "5")
# Delete the cache, add the sleep above and run sanitycheck with a
# large number of JOBS. Once it's done look at the log.txt file
# below and you will see that concurrent cmake processes created the
# same files multiple times.

# While there are a number of reasons why this race seems both very
# unlikely and harmless, let's play it safe anyway and write to a
# private, temporary file first. All modern filesystems seem to
# support at least one atomic rename API and cmake's file(RENAME
# ...) officially leverages that.
string(RANDOM LENGTH 8 tempsuffix)

"${key_path}_tmp_${tempsuffix}" "${key_path}"

# Populate a metadata file (only intended for trouble shooting)
# with information about the hash, the toolchain capability

0 comments on commit f098b44

Please sign in to comment.
You can’t perform that action at this time.