diff options
author | Mark Rutland <mark.rutland@arm.com> | 2021-11-29 14:06:44 +0100 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2021-12-01 00:06:43 +0100 |
commit | 6ce895128b3bff738fe8d9dd74747a03e319e466 (patch) | |
tree | d8585eb931fe75bba40f3cbaf0edc85ab40edd7e /kernel/crash_core.c | |
parent | x86: Snapshot thread flags (diff) | |
download | linux-6ce895128b3bff738fe8d9dd74747a03e319e466.tar.xz linux-6ce895128b3bff738fe8d9dd74747a03e319e466.zip |
entry: Snapshot thread flags
Some thread flags can be set remotely, and so even when IRQs are disabled,
the flags can change under our feet. Generally this is unlikely to cause a
problem in practice, but it is somewhat unsound, and KCSAN will
legitimately warn that there is a data race.
To avoid such issues, a snapshot of the flags has to be taken prior to
using them. Some places already use READ_ONCE() for that, others do not.
Convert them all to the new flag accessor helpers.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Paul E. McKenney <paulmck@kernel.org>
Link: https://lore.kernel.org/r/20211129130653.2037928-3-mark.rutland@arm.com
Diffstat (limited to 'kernel/crash_core.c')
0 files changed, 0 insertions, 0 deletions