summaryrefslogtreecommitdiff
path: root/crypto/algif_rng.c
diff options
context:
space:
mode:
authorMark Rutland <mark.rutland@arm.com>2021-11-29 16:06:46 +0300
committerThomas Gleixner <tglx@linutronix.de>2021-12-01 02:06:43 +0300
commit7fb2b24bb5c5876a3205cb5b9a580f81e8c9f744 (patch)
tree38b8491a93445a4ea2b3454f077b1d70062888d2 /crypto/algif_rng.c
parent0569b245132c40015281610353935a50e282eb94 (diff)
downloadlinux-7fb2b24bb5c5876a3205cb5b9a580f81e8c9f744.tar.xz
alpha: 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> Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru> Cc: Matt Turner <mattst88@gmail.com> Cc: Richard Henderson <rth@twiddle.net> Link: https://lore.kernel.org/r/20211129130653.2037928-5-mark.rutland@arm.com
Diffstat (limited to 'crypto/algif_rng.c')
0 files changed, 0 insertions, 0 deletions