985faa7868
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: Benjamin Herrenschmidt <benh@kernel.crashing.org> Cc: Michael Ellerman <mpe@ellerman.id.au> Cc: Paul Mackerras <paulus@samba.org> Link: https://lore.kernel.org/r/20211129130653.2037928-11-mark.rutland@arm.com |
||
---|---|---|
.. | ||
Makefile | ||
ptrace-adv.c | ||
ptrace-altivec.c | ||
ptrace-decl.h | ||
ptrace-fpu.c | ||
ptrace-noadv.c | ||
ptrace-novsx.c | ||
ptrace-spe.c | ||
ptrace-tm.c | ||
ptrace-view.c | ||
ptrace-vsx.c | ||
ptrace.c | ||
ptrace32.c |