Re: [PATCH] seccomp: Make seccomp.sh re-entrancy safe

On Wed, 21 Jun 2023 13:06:37 +1000 David Gibson wrote:

seccomp.sh generates seccomp.h piece by piece using >> directives. This means that if two instances of seccomp.h are run concurrently a corrupted version of seccomp.h will be generated. Amongst other problems this can cause spurious failures on clang-tidy.

Alter seccomp.sh to build the output in a temporary file and atomic move it to seccomp.h, so concurrent invocations will still result in valud output.

Signed-off-by: David Gibson

Applied. -- Stefano