The reported problem with integrity verification on ARM64 (#269) is a result of a very tight race condition with tracepoints. Changes which simplify synchronization with JUMP_LABEL engine: f98da1b17c01c168ec163b0349327661adc9e38d
affected differently ARM64 platform which made such race possible. However, potentially the same race problem may exist on x86 and this commit fixes it and should address #269
How Has This Been Tested?
I've run various stress manual tests on:
ARM64: using Raspberry Pi 4 (under the kernel 6.5.0-1005-raspi)
x86: using various kernels from Ubuntu 23.10 and 22.04.3, custom kernel 6.3.4 and CentOS 8 (kernel 4.18.0-240.15.1.el8_3.x86_64)
The reported problem with integrity verification on ARM64 (#269) is a result of a very tight race condition with tracepoints. Changes which simplify synchronization with JUMP_LABEL engine: f98da1b17c01c168ec163b0349327661adc9e38d affected differently ARM64 platform which made such race possible. However, potentially the same race problem may exist on x86 and this commit fixes it and should address #269
How Has This Been Tested?
I've run various stress manual tests on: