microblaze: Snapshot thread flags
authorMark Rutland <mark.rutland@arm.com>
Mon, 29 Nov 2021 13:06:49 +0000 (13:06 +0000)
committerThomas Gleixner <tglx@linutronix.de>
Tue, 30 Nov 2021 23:06:44 +0000 (00:06 +0100)
commite538c5849143a7f0aa97006cd45ce4c0c26d0744
tree58738b28e029566b02270b88fc53ef75b836d6b1
parent342b3808786518ced347f40b59bae68664e20007
microblaze: 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>
Tested-by: Michal Simek <michal.simek@xilinx.com>
Acked-by: Paul E. McKenney <paulmck@kernel.org>
Link: https://lore.kernel.org/r/20211129130653.2037928-8-mark.rutland@arm.com
arch/microblaze/kernel/signal.c